Method and apparatus for improving precoding resource block group in a wireless communication system

ABSTRACT

A method and apparatus are disclosed from the perspective of a UE. In one embodiment, the method includes the UE receiving a configuration of functionality of PRB bundling from a base station. The method also includes the UE receiving an indication from the base station regarding whether the functionality of PRB bundling is applied to a TTI or not.

PRIORITY

The present Application is a continuation of U.S. patent applicationSer. No. 15/952,894 filed Apr. 13, 2018, which claims the benefit ofU.S. Provisional Patent Application Ser. No. 62/488,226 filed on Apr.21, 2017, and the entire disclosure of the foregoing applications ishereby incorporated herein in its entirety by reference.

FIELD

This disclosure generally relates to wireless communication networks,and more particularly, to a method and apparatus for improving precodingresource block group in a wireless communication system.

BACKGROUND

With the rapid rise in demand for communication of large amounts of datato and from mobile communication devices, traditional mobile voicecommunication networks are evolving into networks that communicate withInternet Protocol (IP) data packets. Such IP data packet communicationcan provide users of mobile communication devices with voice over IP,multimedia, multicast and on-demand communication services.

An exemplary network structure is an Evolved Universal Terrestrial RadioAccess Network (E-UTRAN). The E-UTRAN system can provide high datathroughput in order to realize the above-noted voice over IP andmultimedia services. A new radio technology for the next generation(e.g., 5G) is currently being discussed by the 3GPP standardsorganization. Accordingly, changes to the current body of 3GPP standardare currently being submitted and considered to evolve and finalize the3GPP standard.

SUMMARY

A method and apparatus are disclosed from the perspective of a UE (UserEquipment). In one embodiment, the method includes the UE receiving aconfiguration of functionality of physical resource block (PRB) bundlingfrom a base station. The method also includes the UE receiving anindication from the base station regarding whether the functionality ofPRB bundling is applied to a transmission time interval (TTI) or not.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a wireless communication system according toone exemplary embodiment.

FIG. 2 is a block diagram of a transmitter system (also known as accessnetwork) and a receiver system (also known as user equipment or UE)according to one exemplary embodiment.

FIG. 3 is a functional block diagram of a communication system accordingto one exemplary embodiment.

FIG. 4 is a functional block diagram of the program code of FIG. 3according to one exemplary embodiment.

FIG. 5 is a reproduction of FIG. 6.2.2-1 of 3GPP TS 36.211 V13.1.0.

FIG. 6 is a reproduction of Table 6.2.3-1 of 3GPP TS 36.211 V13.1.0.

FIG. 7 is a reproduction of Table 6.12-1 of 3GPP TS 36.211 V13.1.0.

FIG. 8 is a reproduction of FIG. 6.13-1 of 3GPP TS 36.211 V13.1.0.

FIG. 9 is a reproduction of Table 6.11.1.1-1 of 3GPP TS 36.211 V13.1.0.

FIG. 10 is a reproduction of Table 6.11.2.1-1 of 3GPP TS 36.211 V13.1.0.

FIG. 11 is a reproduction of Table 6.6.2-1 of 3GPP TS 36.211 V13.1.0.

FIG. 12 is a reproduction of Table 6.6.4-1 of 3GPP TS 36.211 V13.1.0.

FIG. 13 is a reproduction of Table 6.6.4-2 of 3GPP TS 36.211 V13.1.0.

FIG. 14A is a reproduction of FIG. 6.10.1.2-1 of 3GPP TS 36.211 V13.1.0.

FIG. 14B is a reproduction of FIG. 6.10.1.2-2 of 3GPP TS 36.211 V13.1.0.

FIG. 15 is a reproduction of Table 7.1.6.5-1 of 3GPP TS 36.213 V13.1.1.

FIG. 16 is a diagram according to one exemplary embodiment.

FIG. 17 is a diagram according to one exemplary embodiment.

FIG. 18 is a diagram according to one exemplary embodiment.

FIG. 19 is a diagram according to one exemplary embodiment.

FIG. 20 is a diagram according to one exemplary embodiment.

FIG. 21 is a diagram according to one exemplary embodiment.

FIG. 22 is a diagram according to one exemplary embodiment.

FIG. 23 is a diagram according to one exemplary embodiment.

FIG. 24 is a diagram according to one exemplary embodiment.

FIG. 25 is a diagram according to one exemplary embodiment.

FIG. 26 is a diagram according to one exemplary embodiment.

FIG. 27 is a diagram according to one exemplary embodiment.

FIG. 28 is a flow chart according to one exemplary embodiment.

FIG. 29 is a flow chart according to one exemplary embodiment.

FIG. 30 is a flow chart according to one exemplary embodiment.

FIG. 31 is a flow chart according to one exemplary embodiment.

FIG. 32 is a flow chart according to one exemplary embodiment.

FIG. 33 is a flow chart according to one exemplary embodiment.

FIG. 34 is a flow chart according to one exemplary embodiment.

FIG. 35 is a flow chart according to one exemplary embodiment.

FIG. 36 is a flow chart according to one exemplary embodiment.

FIG. 37 is a flow chart according to one exemplary embodiment.

FIG. 38 is a flow chart according to one exemplary embodiment.

DETAILED DESCRIPTION

The exemplary wireless communication systems and devices described belowemploy a wireless communication system, supporting a broadcast service.Wireless communication systems are widely deployed to provide varioustypes of communication such as voice, data, and so on. These systems maybe based on code division multiple access (CDMA), time division multipleaccess (TDMA), orthogonal frequency division multiple access (OFDMA),3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A orLTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra MobileBroadband), WiMax, or some other modulation techniques.

In particular, the exemplary wireless communication systems devicesdescribed below may be designed to support one or more standards such asthe standard offered by a consortium named “3rd Generation PartnershipProject” referred to herein as 3GPP, including: RP-150465, “New SIproposal: Study on Latency reduction techniques for LTE”, Ericsson,Huawei; TS 36.211 V13.1.0, “E-UTRA Physical channels and modulation(Release 13)”; TS 36.212 v13.1.0, “Evolved Universal Terrestrial RadioAccess (E-UTRA); Multiplexing and channel coding (Release 13)”; TS36.213 v13.1.1, “E-UTRA Physical layer procedures (Release 13)”; TS36.331 V14.1.0, “E-UTRA Radio Resource Control (Release 14)”; andR4-1610920, WF on channel bandwidth and transmission bandwidthconfiguration for NR, NTT DOCOMO. The standards and documents listedabove are hereby expressly incorporated by reference in their entirety.

FIG. 1 shows a multiple access wireless communication system accordingto one embodiment of the invention. An access network 100 (AN) includesmultiple antenna groups, one including 104 and 106, another including108 and 110, and an additional including 112 and 114. In FIG. 1, onlytwo antennas are shown for each antenna group, however, more or fewerantennas may be utilized for each antenna group. Access terminal 116(AT) is in communication with antennas 112 and 114, where antennas 112and 114 transmit information to access terminal 116 over forward link120 and receive information from access terminal 116 over reverse link118. Access terminal (AT) 122 is in communication with antennas 106 and108, where antennas 106 and 108 transmit information to access terminal(AT) 122 over forward link 126 and receive information from accessterminal (AT) 122 over reverse link 124. In a FDD system, communicationlinks 118, 120, 124 and 126 may use different frequency forcommunication. For example, forward link 120 may use a differentfrequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access network. Inthe embodiment, antenna groups each are designed to communicate toaccess terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmittingantennas of access network 100 may utilize beamforming in order toimprove the signal-to-noise ratio of forward links for the differentaccess terminals 116 and 122. Also, an access network using beamformingto transmit to access terminals scattered randomly through its coveragecauses less interference to access terminals in neighboring cells thanan access network transmitting through a single antenna to all itsaccess terminals.

An access network (AN) may be a fixed station or base station used forcommunicating with the terminals and may also be referred to as anaccess point, a Node B, a base station, an enhanced base station, anevolved Node B (eNB), or some other terminology. An access terminal (AT)may also be called user equipment (UE), a wireless communication device,terminal, access terminal or some other terminology.

FIG. 2 is a simplified block diagram of an embodiment of a transmittersystem 210 (also known as the access network) and a receiver system 250(also known as access terminal (AT) or user equipment (UE)) in a MIMOsystem 200. At the transmitter system 210, traffic data for a number ofdata streams is provided from a data source 212 to a transmit (TX) dataprocessor 214.

In one embodiment, each data stream is transmitted over a respectivetransmit antenna. TX data processor 214 formats, codes, and interleavesthe traffic data for each data stream based on a particular codingscheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and may be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (i.e., symbol mapped) basedon a particular modulation scheme (e.g. BPSK, QPSK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream may be determined byinstructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TXMIMO processor 220, which may further process the modulation symbols(e.g. for OFDM). TX MIMO processor 220 then provides N_(T) modulationsymbol streams to N_(T) transmitters (TMTR) 222 a through 222 t. Incertain embodiments, TX MIMO processor 220 applies beamforming weightsto the symbols of the data streams and to the antenna from which thesymbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. N_(T)modulated signals from transmitters 222 a through 222 t are thentransmitted from N_(T) antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are receivedby N_(R) antennas 252 a through 252 r and the received signal from eachantenna 252 is provided to a respective receiver (RCVR) 254 a through254 r. Each receiver 254 conditions (e.g. filters, amplifies, anddownconverts) a respective received signal, digitizes the conditionedsignal to provide samples, and further processes the samples to providea corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the N_(R) receivedsymbol streams from N_(R) receivers 254 based on a particular receiverprocessing technique to provide N_(T) “detected” symbol streams. The RXdata processor 260 then demodulates, deinterleaves, and decodes eachdetected symbol stream to recover the traffic data for the data stream.The processing by RX data processor 260 is complementary to thatperformed by TX MIMO processor 220 and TX data processor 214 attransmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use(discussed below). Processor 270 formulates a reverse link messagecomprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message is then processed by a TX data processor 238, whichalso receives traffic data for a number of data streams from a datasource 236, modulated by a modulator 280, conditioned by transmitters254 a through 254 r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system250 are received by antennas 224, conditioned by receivers 222,demodulated by a demodulator 240, and processed by a RX data processor242 to extract the reserve link message transmitted by the receiversystem 250. Processor 230 then determines which pre-coding matrix to usefor determining the beamforming weights then processes the extractedmessage.

Turning to FIG. 3, this figure shows an alternative simplifiedfunctional block diagram of a communication device according to oneembodiment of the invention. As shown in FIG. 3, the communicationdevice 300 in a wireless communication system can be utilized forrealizing the UEs (or ATs) 116 and 122 in FIG. 1 or the base station (orAN) 100 in FIG. 1, and the wireless communications system is preferablythe LTE system. The communication device 300 may include an input device302, an output device 304, a control circuit 306, a central processingunit (CPU) 308, a memory 310, a program code 312, and a transceiver 314.The control circuit 306 executes the program code 312 in the memory 310through the CPU 308, thereby controlling an operation of thecommunications device 300. The communications device 300 can receivesignals input by a user through the input device 302, such as a keyboardor keypad, and can output images and sounds through the output device304, such as a monitor or speakers. The transceiver 314 is used toreceive and transmit wireless signals, delivering received signals tothe control circuit 306, and outputting signals generated by the controlcircuit 306 wirelessly. The communication device 300 in a wirelesscommunication system can also be utilized for realizing the AN 100 inFIG. 1.

FIG. 4 is a simplified block diagram of the program code 312 shown inFIG. 3 in accordance with one embodiment of the invention. In thisembodiment, the program code 312 includes an application layer 400, aLayer 3 portion 402, and a Layer 2 portion 404, and is coupled to aLayer 1 portion 406. The Layer 3 portion 402 generally performs radioresource control. The Layer 2 portion 404 generally performs linkcontrol. The Layer 1 portion 406 generally performs physicalconnections.

Packet data latency is one of the important metrics for performanceevaluation. Reducing packet data latency improves the systemperformance. In 3GPP RP-150465, the study item “study on latencyreduction techniques for LTE” aims to investigate and standardize sometechniques of latency reduction.

According to 3GPP RP-150465, the objective of the study item is to studyenhancements to the E-UTRAN radio system in order to significantlyreduce the packet data latency over the LTE Uu air interface for anactive UE and significantly reduce the packet data transport round triplatency for UEs that have been inactive for a longer period (inconnected state). The study area includes resource efficiency, includingair interface capacity, battery lifetime, control channel resources,specification impact and technical feasibility. Both FDD (FrequencyDivision Duplex) and TDD (Time Division Duplex) duplex modes areconsidered.

According to 3GPP RP-150465, two following areas should be studies anddocumented:

Fast Uplink Access Solutions

For active UEs and UEs that have been inactive a longer time, but arekept in RRC (Radio Resource Control) Connected, focus should be onreducing user plane latency for the scheduled UL (Uplink) transmissionand getting a more resource efficient solution with protocol andsignaling enhancements, compared to the pre-scheduling solutions allowedby the standard today, both with and without preserving the current TTI(Transmission Time Interval) length and processing times.

TTI Shortening and Reduced Processing Times

Assess specification impact and study feasibility and performance of TTIlengths between 0.5 ms and one OFDM (Orthogonal Frequency DivisionMultiplexing) symbol, taking into account impact on reference signalsand physical layer control signaling.

TTI shortening and processing time reduction can be considered as aneffective solution for reducing latency, as the time unit fortransmission can be reduced, e.g. from 1 ms (14 OFDM) symbol to 1-7 OFDMsymbols, and the delay caused by decoding can be reduced as well.Another benefit of shortening TTI length is to support a finergranularity of transport block (TB) size, so that unnecessary paddingcould be reduced. On the other hand, reducing the length of TTI may alsohave significant impact to current system design as the physicalchannels are developed based on 1 ms structure. A shortened TTI is alsocalled a sTTI.

Frame structure used in New RAT (NR) for 5G, to accommodate various typeof requirement (as discussed in 3GPP RP-150465) for time and frequencyresource, e.g. from ultra-low latency (−0.5 ms) to delay-toleranttraffic for MTC (Machine-Type Communication), from high peak rate foreMBB (enhance Mobile Broadband)to very low data rate for MTC. Animportant focus of this study is low latency aspect, e.g. short TTI,while other aspect of mixing/adapting different TTIs can also beconsidered in the study. In addition to diverse services andrequirements, forward compatibility is an important consideration ininitial NR frame structure design as not all features of NR would beincluded in the beginning phase/release.

Reducing latency of protocol is an important improvement betweendifferent generations/releases, which can improve efficiency as well asmeeting new application requirements, e.g. real-time service. Aneffective method frequently adopted to reduce latency is to reduce thelength of TTIs, from 10 ms in 3G to 1 ms in LTE. In the context of LTE-APro in RE1-14, SI/WI was proposed to reduce the TTI to sub-ms level,e.g. 0.1-0.5 ms, by reducing the number of OFDM symbols within a TTI,without changing any existing LTE numerology, i.e. in LTE there is onlyone numerology. The target of this improvement can be to solve the TCPslow start issue, extremely low but frequent traffic, or to meetforeseen ultra-low latency in NR to some extent. Processing timereduction is another consideration to reduce the latency. It has not yetconcluded that whether short TTI and short processing time always cometogether. The study suffers from some limitation, as the method adoptedshould preserve backward compatibility, e.g. the existence of legacycontrol region.

A brief description of LTE numerology is given in 3GPP TS 36.211 asfollows:

6. Downlink 6.1 Overview

The smallest time-frequency unit for downlink transmission is denoted aresource element and is defined in clause 6.2.2.

A subset of the downlink subframes in a radio frame on a carriersupporting PDSCH transmission can be configured as MBSFN subframes byhigher layers. Each MBSFN subframe is divided into a non-MBSFN regionand an MBSFN region.

-   -   The non-MBSFN region spans the first one or two OFDM symbols in        an MBSFN subframe where the length of the non-MBSFN region is        given according to Subclause 6.7.    -   The MBSFN region in an MBSFN subframe is defined as the OFDM        symbols not used for the non-MBSFN region.

For frame structure type 3, MBSFN configuration shall not be applied todownlink subframes in which at least one OFDM symbol is not occupied ordiscovery signal is transmitted.

Unless otherwise specified, transmission in each downlink subframe shalluse the same cyclic prefix length as used for downlink subframe #0.

6.1.1 Physical Channels

A downlink physical channel corresponds to a set of resource elementscarrying information originating from higher layers and is the interfacedefined between 3GPP TS 36.212 [3] and the present document 3GPP TS36.211.

The following downlink physical channels are defined:

-   -   Physical Downlink Shared Channel, PDSCH    -   Physical Broadcast Channel, PBCH    -   Physical Multicast Channel, PMCH    -   Physical Control Format Indicator Channel, PCFICH    -   Physical Downlink Control Channel, PDCCH    -   Physical Hybrid ARQ Indicator Channel, PHICH    -   Enhanced Physical Downlink Control Channel, EPDCCH    -   MTC Physical Downlink Control Channel, MPDCCH

6.1.2 Physical Signals

A downlink physical signal corresponds to a set of resource elementsused by the physical layer but does not carry information originatingfrom higher layers. The following downlink physical signals are defined:

-   -   Reference signal    -   Synchronization signal    -   Discovery signal

6.2 Slot Structure and Physical Resource Elements 6.2.1 Resource Grid

The transmitted signal in each slot is described by one or severalresource grids of N_(RB) ^(DL)N_(sc) ^(RB) subcarriers and N_(symb)^(DL) OFDM symbols. The resource grid structure is illustrated in FIG.6.2.2-1. The quantity N_(RB) ^(DL) depends on the downlink transmissionbandwidth configured in the cell and shall fulfil

N_(RB) ^(min,DL)≤N_(RB) ^(DL)≤N_(RB) ^(max,DL)

where N_(RB) ^(min,DL)=6 N_(RB) ^(max,DL)=110 are the smallest andlargest downlink bandwidths, respectively, supported by the currentversion of this specification.

The set of allowed values for N_(RB) ^(DL) is given by 3GPP TS 36.104[6]. The number of OFDM symbols in a slot depends on the cyclic prefixlength and subcarrier spacing configured and is given in Table 6.2.3-1.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. For MBSFN referencesignals, positioning reference signals, UE-specific reference signalsassociated with PDSCH and demodulation reference signals associated withEPDCCH, there are limits given below within which the channel can beinferred from one symbol to another symbol on the same antenna port.There is one resource grid per antenna port. The set of antenna portssupported depends on the reference signal configuration in the cell:

-   -   Cell-specific reference signals support a configuration of one,        two, or four antenna ports and are transmitted on antenna ports        p=0, p∈{0,1}, and p∈{0,1,2,3}, respectively.    -   MBSFN reference signals are transmitted on antenna port p=4. The        channel over which a symbol on antenna port p=4 is conveyed can        be inferred from the channel over which another symbol on the        same antenna port is conveyed only if the two symbols correspond        to subframes of the same MBSFN area.    -   UE-specific reference signals associated with PDSCH are        transmitted on antenna port(s) p=5, p=7, p=8, or one or several        of p∈{7,8,9,10,11,12,13,14}. The channel over which a symbol on        one of these antenna ports is conveyed can be inferred from the        channel over which another symbol on the same antenna port is        conveyed only if the two symbols are within the same subframe        and in the same PRG when PRB bundling is used or in the same PRB        pair when PRB bundling is not used.    -   Demodulation reference signals associated with EPDCCH are        transmitted on one or several of p∈{107,108,109,110}. The        channel over which a symbol on one of these antenna ports is        conveyed can be inferred from the channel over which another        symbol on the same antenna port is conveyed only if the two        symbols are in the same PRB pair.    -   Positioning reference signals are transmitted on antenna port        p=6. The channel over which a symbol on antenna port p=6 is        conveyed can be inferred from the channel over which another        symbol on the same antenna port is conveyed only within one        positioning reference signal occasion consisting of N_(PRS)        consecutive downlink subframes, where N_(PRS) is configured by        higher layers.    -   CSI reference signals support a configuration of one, two, four,        eight, twelve, or sixteen antenna ports and are transmitted on        antenna ports p=15, p=15,16, p=15, . . . ,18, p=15, . . . ,22,        p=15, . . . ,26 and p=15, . . . ,30, respectively.

Two antenna ports are said to be quasi co-located if the large-scaleproperties of the channel over which a symbol on one antenna port isconveyed can be inferred from the channel over which a symbol on theother antenna port is conveyed. The large-scale properties include oneor more of delay spread, Doppler spread, Doppler shift, average gain,and average delay.

6.2.2 Resource Elements

Each element in the resource grid for antenna port p is called aresource element and is uniquely identified by the index pair (k,l) in aslot where k=0, . . . ,N_(RB) ^(DL)N_(sc) ^(RB)−1 and l=0, . . . ,N_(symb) ^(DL)−1 are the indices in the frequency and time domains,respectively. Resource element (k,l) on antenna port p corresponds tothe complex value α_(k,l) ^((p)).

When there is no risk for confusion, or no particular antenna port isspecified, the index p may be dropped.

[FIG. 6.2.2-1 of 3GPP TS 36.211 V13.1.0, Entitled “Downlink ResourceGrid”, is Reproduced as FIG. 5] 6.2.3 Resource Blocks

Resource blocks are used to describe the mapping of certain physicalchannels to resource elements. Physical and virtual resource blocks aredefined.

A physical resource block is defined as N_(symb) ^(DL) consecutive OFDMsymbols in the time domain and N_(sc) ^(RB) consecutive subcarriers inthe frequency domain, where N_(symb) ^(DL) and N_(sc) ^(RB) are given by

Table 6.2.3-1. A physical resource block thus consists of N_(symb)^(DL)×N_(sc) ^(RB) resource elements, corresponding to one slot in thetime domain and 180 kHz in the frequency domain. Physical resourceblocks are numbered from 0 to N_(RB) ^(DL)−1 in the frequency domain.The relation between the physical resource block number n_(pRB) in thefrequency domain and resource elements (k,l) in a slot is given by

$n_{PRB} = \left\lfloor \frac{k}{N_{sc}^{RB}} \right\rfloor$

[Table 6.2.3-1 of 3GPP TS 36.211 V13.1.0, Entitled “Physical ResourceBlocks Parameters”, is Reproduced as FIG. 6]

A physical resource-block pair is defined as the two physical resourceblocks in one subframe having the same physical resource-block numbern_(PRB).

A virtual resource block is of the same size as a physical resourceblock. Two types of virtual resource blocks are defined:

-   -   Virtual resource blocks of localized type    -   Virtual resource blocks of distributed type

For each type of virtual resource blocks, a pair of virtual resourceblocks over two slots in a subframe is assigned together by a singlevirtual resource block number, n_(VRB).

[. . . .]

6.12 OFDM Baseband Signal Generation

The time-continuous signal s_(l) ^((p))(t) on antenna port p in OFDMsymbol l in a downlink slot is defined by

${s_{l}^{(p)}(t)} = {{\sum\limits_{k = {- {\lfloor{N_{RB}^{DL}N_{sc}^{RB}\text{/}2}\rfloor}}}^{- 1}\;{a_{k^{( - )},l}^{(p)} \cdot e^{j\; 2\pi\; k\;\Delta\;{f{({t - {N_{{CP},l}T_{s}}})}}}}} + {\sum\limits_{k = 1}^{\lceil{N_{RB}^{DL}N_{sc}^{RB}\text{/}2}\rceil}\;{a_{k^{( + )},l}^{(p)} \cdot e^{j\; 2\pi\; k\;\Delta\;{f{({t - {N_{{CP},l}T_{s}}})}}}}}}$

for 0≤t<(N_(CP,l)+N×T_(s) where k⁽⁻⁾=k+└N_(RB) ^(DL)N_(sc) ^(RB)/2┘ andk⁽⁺⁾=k+└N_(RB) ^(DL)N_(sc) ^(RB)/2┘−1. The variable N equals 2048 forΔf=15 kHz subcarrier spacing and 4096 for Δf=7.5 kHz subcarrier spacing.The OFDM symbols in a slot shall be transmitted in increasing order ofl, starting with l=0, where OFDM symbol l>0 starts at time Σ_(l′=0)^(l−1)(N_(CP,l′)+N)T_(s) within the slot. In case the first OFDMsymbol(s) in a slot use normal cyclic prefix and the remaining OFDMsymbols use extended cyclic prefix, the starting position the OFDMsymbols with extended cyclic prefix shall be identical to those in aslot where all OFDM symbols use extended cyclic prefix. Thus there willbe a part of the time slot between the two cyclic prefix regions wherethe transmitted signal is not specified.Table 6.12-1 lists the value of N_(CP,l) that shall be used. Note thatdifferent OFDM symbols within a slot in some cases have different cyclicprefix lengths.[Table 6.12-1 of 3GPP TS 36.211 V13.1.0, entitled “OFDM parameters”, isreproduced as FIG. 7]

6.13 Modulation and Upconversion

Modulation and upconversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 6.13-1. The filtering required prior to transmission is defined bythe requirements in 3GPP TS 36.104 [6].

[FIG. 6.13-1 of 3GPP TS 36.211 V13.1.0, Entitled “Downlink Modulation”,is Reproduced as FIG. 8]

In LTE, there is only one DL numerology defined for initial access,which is 15 KHz subcarrier spacing and the signal and channel to beacquired during initial access is based on 15 KHz numerology. To accessa cell, UE may need to acquire some fundamental information. Forexample, UE first acquires time/frequency synchronization of cell, whichis done during cell search or cell selection/reselection. Thetime/frequency synchronization can be obtained by receivingsynchronization signal, such as primary synchronization signal(PSS)/secondary synchronization signal (SSS). During synchronization,the center frequency of a cell is known, and the subframe/frame boundaryis obtained.

Cyclic prefix (CP) of the cell, e.g. normal CP or extended CP, physicalcell id, duplex mode of the cell, e.g. FDD or TDD can be known as wellwhen PSS (Primary Synchronization Signal)/SSS (Secondary SynchronizationSignal) are acquired. And then, master information block (MIB) carriedon physical broadcast channel (PBCH) is received, some fundamentalsystem information, e.g. system frame number (SFN), system bandwidth,physical control channel related information. UE would receive the DL(downlink) control channel (e.g. PDCCH (Physical Downlink ControlChannel)) on proper resource elements and with proper payload sizeaccording to the system bandwidth and can acquire some more systeminformation required to access the cell in system information block(SIB), such as whether the cell can be access, UL bandwidth andfrequency, random access parameter, and so on.

UE then can perform random access and request the connection to thecell. Cell specific reference signal (CRS) can be used for demodulatingabove mentioned DL channel, e.g. PBCH, DL control channel, or DL datachannel. CRS can also be used to perform measurement for a cell/carriersince the power/content of CRS is known after reading MIB/SIB asmentioned above. After the connection set up is complete, UE would enterconnected mode and be able to perform data transmission to the cell orperform data reception from the cell. The resource allocation for datareception and transmission is done according to system bandwidth (e.g.N_(RB) ^(DL) or N_(RB) ^(UL) in the following quotation) signaled in MIBor SIB. More details can be found in

3GPP TS 36.211, TS 36.212, TS 36.213, and TS 36.331 provide additionaldetails as follows:

6.11 Synchronization Signals

There are 504 unique physical-layer cell identities. The physical-layercell identities are grouped into 168 unique physical-layer cell-identitygroups, each group containing three unique identities. The grouping issuch that each physical-layer cell identity is part of one and only onephysical-layer cell-identity group. A physical-layer cell identityN_(ID) ^(cell)=3N_(ID) ⁽¹⁾+N_(ID) ⁽²⁾ is thus uniquely defined by anumber N_(ID) ⁽¹⁾ in the range of 0 to 167, representing thephysical-layer cell-identity group, and a number N_(ID) ⁽²⁾ in the rangeof 0 to 2, representing the physical-layer identity within thephysical-layer cell-identity group.

6.11.1 Primary Synchronization Signal (PSS) 6.11.1.1 Sequence Generation

The sequence d(n) used for the primary synchronization signal isgenerated from a frequency-domain Zadoff-Chu sequence according to

${d_{u}(n)} = \left\{ \begin{matrix}e^{{- j}\frac{\pi\;{{un}{({n + 1})}}}{63}} & {{n = 0},1,\ldots\;,30} \\e^{{- j}\frac{\pi\;{u{({n + 1})}}{({n + 2})}}{62}} & {{n = 31},32,\ldots\;,61}\end{matrix} \right.$

where the Zadoff-Chu root sequence index u is given by Table 6.11.1.1-1.

[Table 6.11.1.1-1 of 3GPP TS 36.211 V13.1.0, Entitled “Root Indices forthe Primary Synchronization Signal”, is Reproduced as FIG. 9] 6.11.1.2Mapping to Resource Elements

The mapping of the sequence to resource elements depends on the framestructure. The UE shall not assume that the primary synchronizationsignal is transmitted on the same antenna port as any of the downlinkreference signals. The UE shall not assume that any transmissioninstance of the primary synchronization signal is transmitted on thesame antenna port, or ports, used for any other transmission instance ofthe primary synchronization signal.

The sequence d(n) shall be mapped to the resource elements according to

a_(k, l) = d(n), n = 0, … , 61$k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}$

For frame structure type 1, the primary synchronization signal shall bemapped to the last OFDM symbol in slots 0 and 10.

For frame structure type 2, the primary synchronization signal shall bemapped to the third OFDM symbol in subframes 1 and 6. Resource elements(k,l) in the OFDM symbols used for transmission of the primarysynchronization signal where

$k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}$n = −5, −4, … , −1, 62, 63, …66

are reserved and not used for transmission of the primarysynchronization signal.

For frame structure type 3, the primary synchronization signal shall bemapped according to frame structure type 1 with the followingexceptions:

-   -   the primary synchronization signal shall be transmitted only if        the corresponding subframe is non-empty and at least 12 OFDM        symbols are transmitted,    -   a primary synchronization signal being part of a discovery        signal shall be transmitted in the last OFDM symbol of the first        slot of a discovery signal occasion.

6.11.2 Secondary Synchronization Signal (SSS) 6.11.2.1 SequenceGeneration

The sequence d(0), . . . , d(61) used for the second synchronizationsignal is an interleaved concatenation of two length-31 binarysequences. The concatenated sequence is scrambled with a scramblingsequence given by the primary synchronization signal.

The combination of two length-31 sequences defining the secondarysynchronization signal differs between subframes according to

${d\left( {2n} \right)} = \left\{ {{\begin{matrix}{{s_{0}^{(m_{0})}(n)}{c_{0}(n)}} & {{{in}\mspace{14mu}{subframes}\mspace{14mu} 0},1,2,3,4} \\{{s_{1}^{(m_{1})}(n)}{c_{0}(n)}} & {{{in}\mspace{14mu}{subframes}\mspace{14mu} 5},6,7,8,9}\end{matrix}{d\left( {{2n} + 1} \right)}} = \left\{ \begin{matrix}{{s_{1}^{(m_{1})}(n)}{c_{1}(n)}{z_{1}^{(m_{1})}(n)}} & {{{in}\mspace{14mu}{subframes}\mspace{14mu} 0},1,2,3,4} \\{{s_{0}^{(m_{0})}(n)}{c_{1}(n)}{z_{1}^{(m_{1})}(n)}} & {{{in}\mspace{14mu}{subframes}\mspace{14mu} 5},6,7,8,9}\end{matrix} \right.} \right.$

where 0≤n≤30. The indices m₀ and m₁ are derived from the physical-layercell-identity group N_(ID) ⁽¹⁾ according to

m₀ = m^(′)mod 31 m₁ = (m₀ + ⌊m^(′)/31⌋ + 1)mod 31${m^{\prime} = {N_{ID}^{(1)} + {{q\left( {q + 1} \right)}\text{/}2}}},{q = \left\lfloor \frac{N_{ID}^{(1)} + {{q^{\prime}\left( {q^{\prime} + 1} \right)}\text{/}2}}{30} \right\rfloor},{q^{\prime} = \left\lfloor {N_{ID}^{(1)}\text{/}30} \right\rfloor}$

where the output of the above expression is listed in Table 6.11.2.1-1.

The two sequences s₀ ^((m) ⁰ ⁾(n) and s₁ ^((m) ¹ ⁾(n) are defined as twodifferent cyclic shifts of the m-sequence {tilde over (s)}(n) accordingto

s ₀ ^((m) ⁰ ⁾(n)={tilde over (s)}((n+m ₀)mod31)

s ₁ ^((m) ¹ ⁾(n)={tilde over (s)}((n+m ₁)mod31)

where {tilde over (s)}(i)=1−2x(i), 0≤i≤30, is defined by

x(ī+5)=(x(ī+2)+x(i))mod 2, 0≤ī≤25

with initial conditions x(0)=0, x(1)=0, x(2)=0, x(3)=0, x(4)=1.

The two scrambling sequences c₀(n) and c₁(n) depend on the primarysynchronization signal and are defined by two different cyclic shifts ofthe m-sequence c(n) according to

${c_{0}(n)} = {\overset{\sim}{c}\left( {\left( {n + N_{ID}^{(2)}} \right){mod}\; 31} \right)}$${c_{1}(n)} = {\overset{\sim}{c}\left( {\left( {n + N_{ID}^{(2)} + 3} \right){mod}\; 31} \right)}$

where N_(ID) ⁽²⁾∈{0,1,2} is the physical-layer identity within thephysical-layer cell identity group N_(Id) ⁽¹⁾ and {tilde over(c)}(i)=1−2x(i), 0≤i≤30, is defined by

x(ī+5)=(x(ī+3)+x(ī))mod2, 0≤i≤25

with initial conditions x(0)=0, x(1)=0, x(2)=0, x(3)=0, x(4)=1.

The scrambling sequences z₁ ^((m) ⁰ ⁾(n) and z₁ ^((m) ¹ ⁾(n) are definedby a cyclic shift of the m-sequence

z ₁ ^((m) ⁰ ⁾(n)={tilde over (z)}((n+(m ₀mod8))mod31)

z ₁ ^((m) ¹ ⁾(n)={tilde over (z)}((n+(m ₁mod8))mod31)

where m₀ and m₁ are obtained from Table 6.11.2.1-1 and {tilde over(z)}(i)=1−2x(i), 0≤i≤30, is defined by

x(ī+5)=(x(ī+4)+x(ī+2)+x(ī+1)+x(ī))mod 2, 0≤i≤25

with initial conditions x(0)=0, x(1)=0, x(2)=0, x(3)=0, x(4)=1.[Table 6.11.2.1-1 of 3GPP TS 36.211 V13.1.0, Entitled “Mapping BetweenPhysical-Layer Cell-Identity Group N_(ID) ⁽¹⁾ and the Indices m₀ andm₁”, is Reproduced as FIG. 10]

6.11.2.2 Mapping to Resource Elements

The mapping of the sequence to resource elements depends on the framestructure. In a subframe for frame structure type 1 and 3 and in ahalf-frame for frame structure type 2, the same antenna port as for theprimary synchronization signal shall be used for the secondarysynchronization signal.

The sequence d(n) shall be mapped to resource elements according to

a_(k, l) = d(n), n = 0, … , 61$k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}$$l = \left\{ \begin{matrix}{N_{symb}^{DL} - 2} & {{{in}\mspace{14mu}{slots}\mspace{14mu} 0\mspace{14mu}{and}\mspace{14mu} 10}\mspace{220mu}} & {{for}\mspace{14mu}{frame}\mspace{14mu}{structure}\mspace{14mu}{type}\mspace{14mu} 1} \\{N_{symb}^{DL} - 1} & {{{in}\mspace{14mu}{slots}\mspace{14mu} 1\mspace{14mu}{and}\mspace{14mu} 11}\mspace{220mu}} & {{for}\mspace{14mu}{frame}\mspace{14mu}{structure}\mspace{14mu}{type}\mspace{14mu} 2} \\{N_{symb}^{DL} - 2} & {{in}\mspace{14mu}{slots}\mspace{14mu}{where}\mspace{14mu}{the}\mspace{14mu}{PSS}\mspace{14mu}{is}\mspace{14mu}{transmitted}} & {{for}\mspace{14mu}{frame}\mspace{14mu}{structure}\mspace{14mu}{type}\mspace{14mu} 3}\end{matrix} \right.$

Resource elements (k,l) where

$k = {n - 31 + \frac{N_{RB}^{DL}N_{sc}^{RB}}{2}}$$l = \left\{ {{{\begin{matrix}{N_{symb}^{DL} - 2} & {{{in}\mspace{14mu}{slots}\mspace{14mu} 0\mspace{14mu}{and}\mspace{14mu} 10}\mspace{220mu}} & {{for}\mspace{14mu}{frame}\mspace{14mu}{structure}\mspace{14mu}{type}\mspace{14mu} 1} \\{N_{symb}^{DL} - 1} & {{{in}\mspace{14mu}{slots}\mspace{14mu} 1\mspace{14mu}{and}\mspace{14mu} 11}\mspace{220mu}} & {{for}\mspace{14mu}{frame}\mspace{14mu}{structure}\mspace{14mu}{type}\mspace{14mu} 2} \\{N_{symb}^{DL} - 2} & {{in}\mspace{14mu}{slots}\mspace{14mu}{where}\mspace{14mu}{the}\mspace{14mu}{PSS}\mspace{14mu}{is}\mspace{14mu}{transmitted}} & {{for}\mspace{14mu}{frame}\mspace{14mu}{structure}\mspace{14mu}{type}\mspace{14mu} 3}\end{matrix}n} = {- 5}},{- 4},\ldots\;,{- 1},62,63,{\ldots 66}} \right.$

are reserved and not used for transmission of the secondarysynchronization signal.

6.11A Discovery Signal

A discovery signal occasion for a cell consists of a period with aduration of

-   -   one to five consecutive subframes for frame structure type 1    -   two to five consecutive subframes for frame structure type 2    -   12 OFDM symbols within one non-empty subframe for frame        structure type 3        where the UE in the downlink subframes may assume presence of a        discovery signal consisting of    -   cell-specific reference signals on antenna port 0 in all        downlink subframes and in DwPTS of all special subframes in the        period for frame structure type 1 and 2    -   cell specific reference signals on antenna port 0 when higher        layer parameters indicate only one configured antenna port for        cell specific reference signals for a serving cell using frame        structure type 3    -   cell specific reference signals on antenna port 0 and antenna        port 1 when higher layer parameters indicate at least two        configured antenna ports for cell specific reference signals for        a serving cell using frame structure type 3    -   cell specific reference signals on antenna port 0 and antenna        port 1 when higher layer configured parameter        presenceAntennaPort1 is signalled to be 1, for a neighbour cell        when using frame structure type 3    -   primary synchronization signal in the first subframe of the        period for frame structure types 1 and 3 or the second subframe        of the period for frame structure type 2,    -   secondary synchronization signal in the first subframe of the        period, and    -   non-zero-power CSI reference signals in zero or more subframes        in the period. The configuration of non-zero-power CSI reference        signals part of the discovery signal is obtained as described in        clause 6.10.5.2

For frame structures 1 and 2 the UE may assume a discovery signaloccasion once every dmtc-Periodicity.

For frame structure type 3, the UE may assume a discovery signaloccasion may occur in any subframe within the discovery signalsmeasurement timing configuration in clause 5.5.2.10 of [9].

For frame structure type 3, simultaneous transmission of a discoverysignal and PDSCH/PDCCH/EPDCCH may occur in subframes 0 and 5 only.

For frame structure type 3, the UE may assume that a discovery signaloccasion occurs in the first subframe containing a primarysynchronization signal, secondary synchronization signal andcell-specific reference signals within the discovery measurement timingconfiguration in clause 5.5.2.10 of [9].

[. . . ]

6.6 Physical Broadcast Channel

The PBCH is not transmitted for frame structure type 3.

6.6.1 Scrambling

The block of bits b(0), . . . , b(M_(bit)−1), where M_(bit), the numberof bits transmitted on the physical broadcast channel, equals 1920 fornormal cyclic prefix and 1728 for extended cyclic prefix, shall bescrambled with a cell-specific sequence prior to modulation, resultingin a block of scrambled bits {tilde over (b)}(0), . . . , {tilde over(b)}(M_(bit)−1) according to

{tilde over (b)}(i)=(b(i(+c(i))mod 2

where the scrambling sequence c(i) is given by clause 7.2. Thescrambling sequence shall be initialised with c_(init)=N_(ID) ^(cell) ineach radio frame fulfilling n_(f) mod 4=0.

6.6.2 Modulation

The block of scrambled bits {tilde over (b)}(0), . . . , {tilde over(b)}(M_(bit)−1) shall be modulated as described in clause 7.1, resultingin a block of complex-valued modulation symbols d(0), . . . , d(M_(symb)−1). Table 6.6.2-1 specifies the modulation mappings applicablefor the physical broadcast channel.

[Table 6.6.2-1 of 3GPP TS 36.211 V13.1.0, Entitled “PBCH ModulationSchemes”, is Reproduced as FIG. 11]

6.6.3 Layer Mapping and Precoding

The block of modulation symbols d(0), . . . , d(M_(symb)−1) shall bemapped to layers according to one of clauses 6.3.3.1 or 6.3.3.3 withM_(symb) ⁽⁰⁾=M_(symb) and precoded according to one of clauses 6.3.4.1or 6.3.4.3, resulting in a block of vectors y(i)=[y⁽⁰⁾(i) . . .y^((p−1))(i)]^(T), i=0, . . . , M_(symb)−1, where y^((p))(i) representsthe signal for antenna port p and where p=0, . . . , P−1 and the numberof antenna ports for cell-specific reference signals P∈{1,2,4}.

6.6.4 Mapping to Resource Elements

The block of complex-valued symbols y^((p))(0), . . . ,y^((p))(M_(symb)−1) for each antenna port is transmitted during 4consecutive radio frames starting in each radio frame fulfilling n_(f)mod 4=0 and shall be mapped in sequence starting with y(0) to resourceelements (k,l) constituting the core set of PBCH resource elements. Themapping to resource elements (k,l) not reserved for transmission ofreference signals shall be in increasing order of first the index k,then the index l in slot 1 in subframe 0 and finally the radio framenumber. The resource-element indices are given by

${k = {\frac{N_{RB}^{DL}N_{sc}^{RB}}{2} - 36 + k^{\prime}}},{k^{\prime} = 0},1,\ldots\;,71$l = 0, 1, … , 3

where resource elements reserved for reference signals shall beexcluded. The mapping operation shall assume cell-specific referencesignals for antenna ports 0-3 being present irrespective of the actualconfiguration. The UE shall assume that the resource elements assumed tobe reserved for reference signals in the mapping operation above but notused for transmission of reference signal are not available for PDSCHtransmission. The UE shall not make any other assumptions about theseresource elements.

If a cell is configured with repetition of the physical broadcastchannel

-   -   symbols mapped to core resource element (k,l) in slot 1 in        subframe 0 within a radio frame n_(f) according to the mapping        operation above, and    -   cell-specific reference signals in OFDM symbols l in slot 1 in        subframe 0 within a radio frame n_(f) with l according to the        mapping operation above        shall additionally be mapped to resource elements (k,l′) in slot        number n′, within radio frame n_(f)−i unless resource element        (k,l′) is used by CSI reference signals.

For frame structure type 1, l′, n′_(s), and i are given by Table6.6.4-1.

For frame structure type 2,

-   -   if N_(RB) ^(DL)>15, l′ and n′_(s) are given by Table 6.6.4-2 and        i=0;    -   if 7≤N_(RB) ^(DL)≤15, l′ and n′_(s) are given by Table 6.6.4-2        and i=0, except that repetitions with n′_(s)=10 and n′_(s)=11        are not applied.

For both frame structure type 1 and frame structure type 2, repetitionof the physical broadcast channel is not applicable if N_(RB) ^(SL)=6.

Resource elements already used for transmission of cell-specificreference signals in absence of repetition shall not be used foradditional mapping of cell-specific reference signals.

[Table 6.6.4-1 of 3GPP TS 36.211 V13.1.0, Entitled “Frame Offset, Slotand Symbol Number Triplets for Repetition of PBCH for Frame StructureType 1”, is Reproduced as FIG. 12] [Table 6.6.4-2 of 3GPP TS 36.211V13.1.0, Entitled “Slot and Symbol Number Pairs for Repetition of PBCHfor Frame Structure Type 2”, is Reproduced as FIG. 13]

[. . . ]

6.10.1 Cell-Specific Reference Signal (CRS)

The UE may assume cell-specific reference signals are, unless otherwisestated in [4, clause 12], transmitted in

-   -   all downlink subframes for frame structure type 1,    -   all downlink subframes and DwPTS for frame structure type 2,    -   non-empty subframes for frame structure type 3        in a cell supporting PDSCH transmission.

Cell-specific reference signals are transmitted on one or several ofantenna ports 0 to 3.

Cell-specific reference signals are defined for Δƒ=15 kHz only.

6.10.1.1 Sequence Generation

The reference-signal sequence r_(l,n) _(s) (m) is defined by

${{r_{l,n_{s}}(m)} = {{\frac{1}{\sqrt{2}}\left( {1 - {2 \cdot {c\left( {2m} \right)}}} \right)} + {j\frac{1}{\sqrt{2}}\left( {1 - {2 \cdot {c\left( {{2m} + 1} \right)}}} \right)}}},{m = 0},1,\ldots\;,{{2N_{RB}^{\max,{DL}}} - 1}$

where n_(s) is the slot number within a radio frame and l is the OFDMsymbol number within the slot. The pseudo-random sequence c(i) isdefined in clause 7.2. The pseudo-random sequence generator shall beinitialised with c_(init)=2¹⁰·(7·(n′_(s)+1)+l+1)·(2·N_(ID)^(cell)+1)+2·N_(ID) ^(cell)+N_(CP) at the start of each OFDM symbolwhere

$n_{s}^{\prime} = \left\{ {{\begin{matrix}{{10\left\lfloor {n_{s}\text{/}10} \right\rfloor} + {n_{s}\mspace{14mu}{mod}\mspace{14mu} 2}} & {{for}\mspace{14mu}{frame}\mspace{14mu}{structure}\mspace{14mu}{type}\mspace{14mu} 3\mspace{14mu}{when}\mspace{14mu}{the}\mspace{14mu}{CRS}\mspace{14mu}{is}\mspace{14mu}{part}\mspace{14mu}{of}\mspace{14mu} a\mspace{14mu}{DRS}} \\{n_{s}\mspace{211mu}} & {{otherwise}\mspace{545mu}}\end{matrix}N_{CP}} = \left\{ \begin{matrix}1 & {{{for}\mspace{14mu}{normal}\mspace{14mu}{CP}}\mspace{20mu}} \\0 & {{for}\mspace{14mu}{extended}\mspace{14mu}{CP}}\end{matrix} \right.} \right.$

6.10.1.2 Mapping to Resource Elements

The reference signal sequence r_(l,n) _(s) (m) shall be mapped tocomplex-valued modulation symbols α_(k,l) ^((p)) used as referencesymbols for antenna port p in slot n_(s) according to

a_(k, l)^((p)) = r_(l, n_(s))(m^(′)) where k = 6m + (v + v_(shift))mod 6$l = \left\{ {{{\begin{matrix}{0,{N_{symb}^{DL} - 3}} & {{{if}\mspace{14mu} p} \in \left\{ {0,1} \right\}} \\{1\mspace{115mu}} & {{{if}\mspace{14mu} p} \in \left\{ {2,3} \right\}}\end{matrix}m} = 0},1,\ldots\;,{{{2 \cdot N_{RB}^{DL}} - {1m^{\prime}}} = {m + N_{RB}^{\max,{DL}} - N_{RB}^{DL}}}} \right.$

The variables v and v_(shift) define the position in the frequencydomain for the different reference signals where v is given by

$v = \left\{ \begin{matrix}{0\mspace{160mu}} & {{{if}\mspace{14mu} p} = {{0\mspace{14mu}{and}\mspace{14mu} l} = 0}} \\{3\mspace{160mu}} & {{{if}\mspace{14mu} p} = {{0\mspace{14mu}{and}\mspace{14mu} l} \neq 0}} \\{3\mspace{160mu}} & {{{if}\mspace{14mu} p} = {{1\mspace{14mu}{and}\mspace{14mu} l} = 0}} \\{0\mspace{160mu}} & {{{if}\mspace{14mu} p} = {{1\mspace{14mu}{and}\mspace{14mu} l} \neq 0}} \\{{3\left( {n_{s}\mspace{14mu}{mod}\mspace{14mu} 2} \right)}\mspace{40mu}} & {{{{if}\mspace{14mu} p} = 2}\mspace{110mu}} \\{3 + {3\left( {n_{s}\mspace{14mu}{mod}\mspace{14mu} 2} \right)}} & {{{{if}\mspace{14mu} p} = 3}\mspace{110mu}}\end{matrix} \right.$

The cell-specific frequency shift is given by v_(shift)=N_(ID) ^(cell)mod 6.

Resource elements (k,l) used for transmission of cell-specific referencesignals on any of the antenna ports in a slot shall not be used for anytransmission on any other antenna port in the same slot and set to zero.

In an MBSFN subframe, cell-specific reference signals shall only betransmitted in the non-MBSFN region of the MBSFN subframe.

FIGS. 6.10.1.2-1 and 6.10.1.2-2 illustrate the resource elements usedfor reference signal transmission according to the above definition. Thenotation R_(p) is used to denote a resource element used for referencesignal transmission on antenna port p.

[FIG. 6.10.1.2-1 of 3GPP TS 36.211 V13.1.0, Entitled “Mapping ofDownlink Reference Signals (Normal Cyclic Prefix), is reproduced as FIG.14A]

[FIG. 6.10.1.2-2 of 3GPP TS 36.211 V13.1.0, Entitled “Mapping ofDownlink Reference Signals (Extended Cyclic Prefix), is Reproduced asFIG. 14B]

[. . . ]

MasterInformationBlock

The MasterInformationBlock includes the system information transmittedon BCH.

Signalling radio bearer: N/A

RLC-SAP: TM

Logical channel: BCCH

Direction: E-UTRAN to UE

MasterInformationBlock -- ASN1START MasterInformationBlock ::= SEQUENCE{ dl-Bandwidth ENUMERATED { n6, n15, n25, n50, n75, n100}, phich-ConfigPHICH-Config, systemFrameNumber BIT STRING (SIZE (8)),schedulingInfoSIB1-BR-r13 INTEGER (0..31), spare BIT STRING (SIZE (5)) }-- ASN1STOP

MasterInformationBlock field descriptions dl-Bandwidth Parameter:transmission bandwidth configuration, N_(RB) in downlink, see TS 36.101[42, table 5.6- 1]. n6 corresponds to 6 resource blocks, n15 to 15resource blocks and so on. phich-Config Specifies the PHICHconfiguration. If the UE is a BL UE or UE in CE, it shall ignore thisfield. schedulingInfoSIB1-BR This field contains an index to a tablethat defines SystemInformationBlockType1-BR scheduling information. Thetable is specified in TS 36.213 [23, Table 7.1.6-1 and Table7.1.7.2.7-1], Value 0 means that SystemInformationBlockType1-BR is notscheduled. systemFrameNumber Defines the 8 most significant bits of theSFN. As indicated in TS 36.211 [21, 6.6.1], the 2 least significant bitsof the SFN are acquired implicitly in the P-BCH decoding, i.e. timing of40ms P- BCH TTI indicates 2 least significant bits (within 40ms P-BCHTTI, the first radio frame: 00, the second radio frame: 01, the thirdradio frame: 10, the last radio frame: 11). One value applies for allserving cells of a Cell Group (i.e. MCG or SCG). The associatedfunctionality is common (i.e. not performed independently for eachcell).

When receiving data, physical resource block (PRB) bundling can beconducted to improve the performance of reception. A set of physicalresource blocks consecutive in frequency domain can be grouped intoprecoding resource block groups (PRGs). When UE is configured with sometransmission mode, or when UE is configured with some channel stateinformation (CSI) reporting type, or when UE is configured with PRBbundling operation, UE could assume the same transmission technic isapplied to resource blocks within a same PRG, e.g. using a same precoderor using a same beam to transmit resource blocks within a same PRG.

Therefore, when UE receive the resource blocks within a same PRG, theprocess of reception can be done jointly as well. For example, when UEdemodulates the resource blocks within a same PRG, channel estimation ofthe PRBs can be done jointly as the PRBs are closed in frequency domainand transmit in a same way so that the channel for the PRBs can beassumed to be identical. For example, if there are three PRBs (includingPRB A, PRB B, and PRB C) within a PRG, reference signals within PRB A,PRB B, and PRB C can all be used to derive the channel and data withinPRB A, PRB B, and PRB C can be demodulated assuming the derived channel.

Comparing with using reference signal within PRB A to derive a channelto demodulate data within PRB A, deriving channel jointly can improvethe accuracy of channel estimation, as the number of resource occupiedby reference signal would be increased to three time in the example.Also, the channel estimation can be more robust given more samples ofreference signal is measured, such that if some resource of referencesignal is interference by other signal, averaging all samples caneliminate the impact of interference. As channel estimation with PRBbundling can be improved, the quality of reception can also be improved,e.g. bit error rate (BER), block error rate (BLER), throughput, or datarate. Additional detail can be found in 3GPP TS 36.213 as follows:

7.1.6.5 Physical Resource Block (PRB) Bundling

A UE configured for transmission mode 9 for a given serving cell c mayassume that precoding granularity is multiple resource blocks in thefrequency domain when PMI/RI reporting is configured.

For a given serving cell c, if a UE is configured for transmission mode10

-   -   if PMI/RI reporting is configured for all configured CSI        processes for the serving cell c, the UE may assume that        precoding granularity is multiple resource blocks in the        frequency domain,    -   otherwise, the UE shall assume the precoding granularity is one        resource block in the frequency domain.

Fixed system bandwidth dependent Precoding Resource block Groups (PRGs)of size P′ partition the system bandwidth and each PRG consists ofconsecutive PRBs. If N_(RB) ^(DL)modP′>0 then one of the PRGs is of sizeN_(RB) ^(DL)−P└N_(RB) ^(DL)/P′┘. The PRG size is non-increasing startingat the lowest frequency. The UE may assume that the same precoderapplies on all scheduled PRBs within a PRG.

If the UE is a BL/CE UE P′=3 otherwise the PRG size a UE may assume fora given system bandwidth is given by:

[Table 7.1.6.5-1 of 3GPP TS 36.213 V13.1.1 is reproduced as FIG. 15]

When it comes to NR, the story becomes somehow different, as backwardcompatibility is not a must. Numerology can be adjusted so that reducingsymbol number of a TTI would not be the only tool to change TTI length.Using LTE numerology as an example, it comprises 14 OFDM symbol in 1 msand a subcarrier spacing of 15 KHz. When the subcarrier spacing goes to30KHz, under the assumption of same FFT size and same CP structure,there would be 28 OFDM symbols in 1 ms, equivalently the TTI become 0.5ms if the number of OFDM symbol in a TTI is kept the same. This impliesthe design between different TTI lengths can be kept common, with goodscalability performed on the subcarrier spacing. Of course there wouldalways be trade-off for the subcarrier spacing selection, e.g. FFT size,definition/number of PRB, the design of CP, supportable systembandwidth, etc. While as NR considers larger system bandwidth, andlarger coherence bandwidth, inclusion of a larger sub carrier spacing isa nature choice.

As discussed above, it is generally very difficult to fulfill alldiverse requirements with a single numerology. Therefore, it is agreedin the very first meeting that more than one numerology would beadopted. Furthermore, considering the standardization effort,implementation efforts, as well as multiplexing capability amongdifferent numerologies, it would be beneficial to have some relationshipbetween different numerologies, such as integral multiple relationship.Several numerology families, were raised, one of them is based on LTE 15KHz, and some other numerologies (Alt2˜4 below) which allows power N of2 symbols in 1 MS:

-   -   For NR, it is necessary to support more than one values of        subcarrier-spacing        -   Values of subcarrier-spacing are derived from a particular            value of subcarrier-spacing multiplied by N where N is an            integer            -   Alt.1: Subcarrier-spacing values include 15 kHz                subcarrier-spacing (i.e., LTE based numerology)            -   Alt.2: Subcarrier-spacing values include 17.5 kHz                subcarrier-spacing with uniform symbol duration                including CP length            -   Alt.3: Subcarrier-spacing values include 17.06 kHz                subcarrier-spacing with uniform symbol duration                including CP length            -   Alt.4: Subcarrier-spacing values 21.33 kHz            -   Note: other alternatives are not precluded            -   FFS: exact value of a particular value and possible                values of N        -   The values of possible subcarrier-spacing will be further            narrowed-down in RAN1#85

Also, whether there would be restriction on the multiplier of a givennumerology family is also discussed, power of 2 (Alt 1 below) drew someinterests as it can multiplex different numerology easier withoutintroducing much overhead when different numerologies is multiplexed intime domain:

-   -   RAN1 will continue further study and conclude between following        alternatives in the next meeting    -   Alt. 1:        -   >The subcarrier spacing for the NR scalable numerology            should scale as        -   >f_(SC)=f₀*2^(m)        -   >where            -   f₀ is FFS            -   m is an integer chosen from a set of possible values    -   Alt. 2:        -   >The subcarrier spacing for the NR scalable numerology            should scale as        -   >f_(SC)=f₀*M        -   >where            -   f₀ is FFS            -   M is an integer chosen from a set of possible positive                values

Usually, RAN1 works as band agnostic manner, i.e. a scheme/feature wouldbe assumed to be applicable for all frequency bands and in the followingRAN4 would derive relevant test case considering if some combination isunrealistic or deployment can be done reasonably. This rule would stillbe assumed in NR, while some companies do see there would be restrictionfor sure as the frequency range of NR is quite high:

-   -   For the study of NR, RAN1 assumes that multiple (but not        necessarily all) OFDM numerologies can apply to the same        frequency range        -   Note: RAN1 does not assume to apply very low value of            subcarrier spacing to very high carrier frequency

Furthermore, the synchronization signal/reference signal design in NRmay be quite different from that in LTE. For example, a synchronizationsignal (e.g. SS block) periodicity may be 10 or 20 ms comparing with 5ms periodicity in LTE. Besides, a base station might adjust thesynchronization signal periodicity to a longer value considering allaspect, e.g. traffic or power consumption, unlike a fixed assumedperiodicity in LTE. Also, CRS which is available in every subframe islikely to be removed from NR considering the huge amount of overhead andconstant power consumption.

Agreements:

-   -   RAN1 considers following parameter sets with associated default        subcarrier spacing and possible maximum transmission bandwidth        for NR-SS design        -   Parameter set #W associated with 15 kHz subcarrier spacing            and NR-SS transmission bandwidth no larger than 5 MHz        -   Parameter set #X associated with 30 kHz subcarrier spacing            and NR-SS transmission bandwidth no larger than 10 MHz        -   Parameter set #Y associated with 120 kHz subcarrier spacing            and NR-SS transmission bandwidth no larger than 40 MHz        -   Parameter set #Z associated with 240 kHz subcarrier spacing            and NR-SS transmission bandwidth no larger than 80 MHz        -   Note that association between a frequency band and single            set of default parameters (SCS, sequence length, NR-SS            transmission bandwidth) will be defined in RAN4        -   Note that each subcarrier spacing is associated with single            sequence length and transmission bandwidth        -   Note that additional parameter set or further down selection            of parameter set is not precluded        -   This agreement does not preclude any subcarrier spacing for            data channel

Agreements:

-   -   For set of possible SS block time locations, further evaluation        till next meeting by considering at least the following:        -   Whether or not a SS block comprises of consecutive symbols            and whether or not SS&PBCH in the same or different slots        -   Number of symbols per SS block        -   Whether or not to map across slot boundary(ies)        -   Whether or not to skip symbol(s) within a slot or a slot set        -   Contents of an SS block (note: the contents of an SS block            may be further discussed during this meeting)        -   How SS blocks are arranged within a burst set, & the # of SS            blocks per burst/burst set

Agreements:

-   -   The maximum number of SS-blocks, L, within SS burst set may be        carrier frequency dependent        -   For frequency range category #A (e.g., 0˜6 GHz), the            number (L) is TBD within L≤[16]        -   For frequency range category #B (e.g., 6˜60 GHz), the number            is TBD within L≤[128]        -   FFS: L for additional frequency range category    -   The position(s) of actual transmitted SS-blocks can be informed        for helping CONNECTED/IDLE mode measurement, for helping        CONNECTED mode UE to receive DL data/control in unused SS-blocks        and potentially for helping IDLE mode UE to receive DL        data/control in unused SS-blocks        -   FFS whether this information is available only in CONNECTED            mode or in both modes        -   FFS how to signal the position(s)

Agreements:

-   -   For detecting non-standalone NR cell, NR should support        adaptation and network indication of SS burst set periodicity        and information to derive measurement timing/duration (e.g.,        time window for NR-SS detection)        -   For detecting non-standalone NR cell, network provides one            SS burst set periodicity information per frequency carrier            to UE and information to derive measurement timing/duration            if possible            -   In case that one SS burst set periodicity and one                information regarding timing/duration are indicated, UE                assumes the periodicity and timing/duration for all                cells on the same carrier            -   RAN1 recommends short measurement duration than                configured periodicity e.g., 1, 5 or 10 ms                -   Note that L1/L3 filtering across multiple periods is                    still allowed            -   FFS more than one periodicity/timing/duration indication        -   NR should support set of SS burst set periodicity values for            adaptation and network indication            -   Candidate periodicity values to be evaluated are [20,                40, 80 and 160 ms]            -   FFS other values with consideration for functionalities                provided by NR-SS in connected mode        -   FFS whether to support NR-PBCH in non-standalone NR cell

Agreements:

-   -   For initial cell selection for NR cell, UE assume the following        default SS burst set periodicity        -   For carrier frequency range category #A: TBD among 10, 20 ms            -   E.g. range for #A (0˜6 GHz)        -   For carrier frequency range category #B: TBD among 10, 20 ms            -   E.g. range for #B (6 GHz˜60 GHz)        -   Down-selection will consider the SS block dimensions,            initial access latency, power consumption, detection            performance aspects into account. Other considerations are            not precluded.        -   Note that this does not preclude further sub-categorization            of frequency ranges. And additional frequency sub-ranges            defined shall support a single default SS burst set            periodicity, value selected between 10, 20 ms        -   Note that this does not preclude additional categorization            of frequency ranges not covered by #A and #B. SS burst set            periodicity for potential additional frequency ranges is FFS        -   RAN4 will determine the exact values of frequency ranges        -   The exact frequency ranges for category #A and #B is subject            to further discussion in RAN1 and RAN1 will provide input to            RAN4 to finalize the exact values.        -   Note that UE is not expected to detect cell that do not            conform to the default SS burst set periodicity        -   RAN1 will definitely down select the values from 10, 20 ms            in the next meeting

Agreements:

-   -   For CONNECTED and IDLE mode UEs, NR should support network        indication of SS burst set periodicity and information to derive        measurement timing/duration (e.g., time window for NR-SS        detection)        -   Network provides one SS burst set periodicity information            per frequency carrier to UE and information to derive            measurement timing/duration if possible            -   In case that one SS burst set periodicity and one                information regarding timing/duration are indicated, UE                assumes the periodicity and timing/duration for all                cells on the same carrier            -   RAN1 recommends shorter measurement duration than                configured periodicity e.g., 1, 5 or 10 ms                -   Note that L1/L3 filtering across multiple periods is                    still allowed            -   FFS more than one periodicity/timing/duration indication        -   If the network does not provide indication of SS burst set            periodicity and information to derive measurement            timing/duration the UE should assume 5 ms as the SS burst            set periodicity        -   NR should support set of SS burst set periodicity values for            adaptation and network indication            -   Candidate periodicity values to be evaluated are [5, 10,                20, 40, 80, and 160 ms]

To fulfill the requirements of data rate, it is expected that NR needsto support a total bandwidth of above 1 GHz. It may be achieved viaaggregating a larger amount of carriers with smaller carrier bandwidthof or via aggregating a smaller amount of carriers with larger carrierbandwidth. Tradeoff between the two options may be complexity andefficiency. While anyway NR would support a much wider bandwidth ofsingle carrier than LTE, e.g. a level of 100 MHz, comparing with amaximum 20 MHz in LTE, which imply there may be some different designconsideration considering such huge different.

One of the key considerations is whether a single baseband (channel)bandwidth or a single RF bandwidth can cover a single carrier. Manyaspects can be considered, such as complexity (e.g. FFT size, samplingrate, PA linearity), or total power, which would result in a differentcombinations of possible implementation. An example of different optionsto cover a wider bandwidth with a smaller bandwidth of a component isgiven in FIG. 16 (as illustrated in 3GPP R4-1610920).

Some relevant discussion took placed in 3GPP:

Agreements:

-   -   At least for Phase 1, study mechanisms to support operation over        e.g. around 1 GHz contiguous spectrum from both NW and UE        perspectives including the maximum single carrier bandwidth of        at least 80 MHz        -   Carrier Aggregation/Dual Connectivity (Multi-carrier            approach)            -   Details are FFS            -   FFS: non-contiguous spectrum case        -   Single carrier operation            -   Details are FFS            -   Maximum channel bandwidth continues to be studied in                RAN1/4                -   Maximum bandwidth supported by some UE capabilities                    or categories may be less than channel bandwidth of                    serving single carrier                -   Note that some UE capabilities or categories may                    support channel bandwidth of serving single carrier    -   Send an LS to ask RAN4 to study the feasibilities of mechanisms        above from both NW and UE perspectives

Agreements:

-   -   Study at least the following aspects for NR carrier        aggregation/dual connectivity        -   Intra-TRP and inter-TRP with ideal and non-ideal backhaul            scenarios        -   Number of carriers        -   The need for certain channels, e.g. downlink control            channel, uplink control channel or PBCH for some carriers        -   Cross-carrier scheduling and joint UCI feedback, e.g.            HARQ-ACK feedback        -   Carrier on/off switching mechanism        -   Power control        -   Different numerologies between different/same carrier(s) for            a given UE            -   FFS: whether/if different numerologies are multiplexed                on one carrier for one UE is called carrier                aggregation/dual connectivity

Agreements:

-   -   NR should provide support for carrier aggregation, including        different carriers having same or different numerologies.

Agreements:

-   -   For phase 1, carrier aggregation/dual connectivity operation        within NR carriers over e.g. around 1 GHz contiguous and        non-contiguous spectrum from both NW and UE perspectives is        supported        -   [4-32] should be assumed for further study of the maximum            number of NR carriers            -   RAN1 will try to decide the exact number in this week        -   Cross-carrier scheduling and joint UCI feedback are            supported        -   Per-carrier TB mapping is supported            -   FFS TB mapping across multiple carriers

Agreements:

-   -   From RAN1 specification perspective, maximum channel bandwidth        per NR carrier is [400, 800, 1000] MHz in Rel-15        -   RAN1 recommends RAN4 to consider at least 100 MHz maximum            channel bandwidth per NR carrier in Rel-15 considering            carrier frequency bands        -   RAN1 asks the feasibility of at least followings            -   For sub-6 GHz, 100 MHz is considered and for above-6                GHz, wider than 100 MHz is considered            -   Other cases can be considered by RAN4, e.g., 40 MHz, 200                MHz        -   Note that RAN1 will specify all details for channel            bandwidth at least up to 100 MHz per NR carrier in Rel-15        -   Also note that RAN1 will consider scalable design(s) for up            to maximum channel bandwidth per NR carrier    -   From RAN1 specification perspective, the maximum number of NR        carriers for CA and DC is [8, 16, 32]    -   The maximum FFT size is not larger than [8192, 4096, 2048]

Agreements:

-   -   If it is decided that maximum CC BW is greater than or equal to        400 MHz and smaller than or equal to 1000 MHz        -   The maximum number of CCs in any aggregation is [either 8 or            16]    -   If it is decided that the maximum CC BW is <=100 MHz        -   The maximum number of CCs in any aggregation could be            [either 16 or 32]    -   If it is decided that the maximum CC BW is greater than 100 MHz        and smaller than 400 MHz        -   The maximum number of CCs is FFS

Agreements:

-   -   From RAN1 specification perspective, maximum channel bandwidth        per NR carrier is 400 MHz in Rel-15        -   Note: final decision on the value is up to RAN4    -   From RAN1 specification perspective, at least for single        numerology case, candidates of the maximum number of subcarriers        per NR carrier is 3300 or 6600 in Rel-15        -   FFS: For mixed numerology case, the above applies to the            lowest subcarrier spacing        -   Note: final value for a given channel BW is up to RAN4            decision    -   From RAN1 specification perspective, the maximum number of NR        carriers for CA and DC is 16        -   Note that 32 is considered from RAN2 specification            perspective        -   The number of NR CCs in any aggregation is independently            configured for downlink and uplink    -   NR channel designs should consider potential future extension of        the above parameters in later releases, allowing Rel-15 UE to        have access to NR network on the same frequency band in later        releases

Agreements:

-   -   Prepare draft LS in R1-1703919—Peter (Qualcomm) to RAN4 to        inform that RAN1 is discussing following alternatives for a        wider BW CC, i.e., CC BW greater than X (e.g., 100 MHz),        -   A) UE is configured with one wideband carrier while the UE            utilizes multiple Rx/Tx chains (Case 3)        -   B) A gNB can operate simultaneously as wideband CC for some            UEs (UEs with single chain) and as a set of intra-band            contiguous CCs with CA for other UEs (UEs with multiple            chains)            -   FFS: Potential impact on design for the wide BW                signal/channels    -   Note: The support of multiple Rx/Tx chains in the gNB within one        wideband CC is not addressed in above discussion

Agreements:

-   -   Resource allocation for data transmission for a UE not capable        of supporting the carrier bandwidth can be derived based on a        two-step frequency-domain assignment process        -   1^(st) step: indication of a bandwidth part        -   2^(nd) step: indication of the PRBs within the bandwidth            part        -   FFS definitions of bandwidth part        -   FFS signaling details    -   FFS the case of a UE capable of supporting the carrier bandwidth

In the following, we provide our view on the details of two stepresource allocation for data channel in NR.

Agreements:

-   -   The duration of a data transmission in a data channel can be        semi-statically configured and/or dynamically indicated in the        PDCCH scheduling the data transmission        -   FFS: the starting/ending position of the data transmission        -   FFS: the indicated duration is the number of symbols        -   FFS: the indicated duration is the number of slots        -   FFS: the indicated duration is the numbers of symbols+slots        -   FFS: in case cross-slot scheduling is used        -   FFS: in case slot aggregation is used        -   FFS: rate-matching details        -   FFS: whether/how to specify UE behavior when the duration of            a data transmission in a data channel for the UE is unknown

Agreement:

-   -   For single-carrier operation,        -   UE is not required to receive any DL signals outside a            frequency range A which is configured to the UE            -   The interruption time needed for frequency range change                from frequency range A to a frequency range B is TBD            -   Frequency ranges A & B may be different in BW and center                frequency in a single carrier operation

Working Assumption:

-   -   One or multiple bandwidth part configurations for each component        carrier can be semi-statically signalled to a UE        -   A bandwidth part consists of a group of contiguous PRBs            -   Reserved resources can be configured within the                bandwidth part        -   The bandwidth of a bandwidth part equals to or is smaller            than the maximal bandwidth capability supported by a UE        -   The bandwidth of a bandwidth part is at least as large as            the SS block bandwidth            -   The bandwidth part may or may not contain the SS block        -   Configuration of a bandwidth part may include the following            properties            -   Numerology            -   Frequency location (e.g. center frequency)            -   Bandwidth (e.g. number of PRBs)        -   Note that it is for RRC connected mode UE        -   FFS how to indicate to the UE which bandwidth part            configuration (if multiple) should be assumed for resource            allocation at a given time        -   FFS neighbour cell RR

Agreement:

-   -   Support the following:        -   A gNB can operate simultaneously as wideband CC for some UEs            and as a set of intra-band contiguous CCs with CA for other            UEs            -   RAN1 believes that it is beneficial to allow zero                guard-band between CCs within wideband CC and asks RAN4                to take it into account when discussing channel raster                -   If there are scenarios where guard band is                    considered necessary, strive to minimize the number                    of subcarriers for guard-band between CCs within                    wideband CC                -   It is RAN1 understanding that guard band might be                    supported by RAN4            -   Allow single or multiple Sync signal locations in                wideband CC    -   Consider further impact on design for:        -   Reference signals        -   Resource Block Group design and CSI subbands

If PRG is applied on a cell with wider bandwidth supported by multipleRF chains, as PRG is counted contiguously across a whole cell, it ispossible that a PRG would map cross different RF bandwidths, e.g. someresource block(s) within a PRG is processed by a RF chain while otherresource block within the PRG is processed by another RF chain. Asdifferent RF chains would induce non-continuity of phase and amplitudefrom each other, demodulating resource blocks belonging to different RFchains jointly would harm accuracy of channel estimation as amplitudeand phase error would be induced by the non-continuity.

In general, the benefit of PRB bundling would then harm thequality/performance of reception in the PRG cross RF (Radio Frequency)boundary. In other words, if a UE is scheduled a PRG mapped cross RFchain boundary and the UE assume all reference signal within the PRG canbe used to derive a channel for demodulation of whole PRG, the receptionwould be degraded as reference signal of one PRB in a PRG in one RFchain cannot be used to obtain channel of another PRB in the PRG inanother RF chain. An example of this issue is given in FIGS. 16 and 17.

In the example, a total of 400 PRBs in one carrier is assumed and thereare three RF chains used to cover the carrier, e.g. in gNB side. 1st RFchain and 2nd RF chain could cover 133 resource blocks and 3rd RF chaincould cover 134 resource blocks. Following current PRG design, startingfrom low frequency to high frequency, size of PRG would be innon-increasing order. That is, 3 PRB would be grouped into a PRG in thisexample and the first PRG to 133th PRG would each comprise 3 PRB and 134th PRG would comprise 1 PRB. It can be observed that following thisdesign, first PRB of 45th PRG would be covered by 1st RF chain and therest two PRBs of 45th PRG would be covered by 2nd RF chain. Similarly,PRBs in 89th PRG would be covered by 2nd RF chain and 3rd RF chain. If45th PRG is within reception bandwidth of a UE and PRBs scheduled to theUE within 45th PRG belongs to different RF chain, deriving channelestimation across PRBs within 45th PRG would be problematic. Note thatin this example, 3PRB per PRG is assumed, while if a larger size of PRGis used, the problem would be even worse, e.g., for 6 or 10 PRBs perPRG.

A first general concept of this invention, according to one exemplaryembodiment, is that gNB (gNodeB) avoids scheduling a PRG which mapscross RF bandwidth boundary at least for UE operating with PRB bundling.gNB can schedule PRG which maps cross RF bandwidth boundary to UE notoperating with PRB bundling. An example is given in FIG. 18.

Similarly while alternatively, gNB can schedule a PRG which maps crossRF bandwidth boundary for UE operating with PRB bundling, while thescheduled PRB within the PRG belong to a single RF chain, e.g. either1st PRB of 45th PRG belonging to 1st RF chain or 2nd 3rd PRB of 45th PRGbelonging to 2nd RF chain in the example. An example is given in FIG.19.

A second general concept would be that gNB avoids PRG mapping cross RFbandwidth boundary. For example, one RF bandwidth consists of integernumber of PRGs. Taking example in FIG. 16 as an example, bandwidth of1st RF chain would be 135 PRBs, i.e. 45 PRGs. Bandwidth of 2nd RFbandwidth can be 135 or 132 PRBs, i.e. 45 or 44 PRGs. The rest PRBs/PRGare covered by 3rd RF bandwidth. An example is given in FIG. 20.

A third general concept is the size of PRG does not follownon-increasing order in frequency domain across the whole carrierbandwidth. For example, within a bandwidth, e.g. RF bandwidth, the sizeof PRG follows non-increasing order in frequency domain, while acrosstwo bandwidths, e.g. cross boundary of two RF bandwidths, the size ofPRG can be increased in frequency domain. For example, 130th˜132th PRBin FIG. 16 can be configured as 44th PRG (with size of 3 PRBs), 133thPRB can be configured as 45th PRG (with size of 1 PRB) and 134th PRB and135th PRB can be configured as 46th PRG (with size of 2 PRBs),136th˜138th PRB can be configured as 47th PRG (with size of 3 PRBs).Examples are given in FIGS. 21 and 22.

A fourth general concept is the PRB to PRG mapping is done per bandwidthportion, e.g. per RF bandwidth. For example, a carrier/cell can bedivided into several bandwidth portions, and each bandwidth portioncomprises a number of PRB(s). Note that different bandwidth portions maycomprise different numbers of PRB(s). A bandwidth portion would bepartitioned by a PRG size. At least one PRG with size less than PRG sizefor the bandwidth portion exists if PRG size cannot be equally dividedby PRG size for the bandwidth portion. Note that PRG size for differentbandwidth portion may be different. PRG size for a given bandwidthportion can be derived according to a predefined rule, e.g. according toa bandwidth of the given bandwidth portion. An example is given in FIG.23.

A fifth general concept is that gNB indicates boundary(s), e.g. RFbandwidth boundary and/or PRB bundling boundary, of a carrier to a UE.The boundary is related to PRB bundling operation. For example, when UEperforms channel estimation according to PRB bundling, UE would derivejoint channel estimation for PRG which does not map across the boundary.UE would not derive joint channel estimation for PRG across theboundary(s). UE would derive separate/different channel estimations forPRB(s) on different side of the boundary(s). An example is given in FIG.24.

A sixth general concept is that gNB can control whether PRB bundling isapplied/turn-on/activated by the UE or not, e.g. gNB can decide to turnon or turn off the PRB bundling functionality in the UE side, an exampleof the decision is whether a PRG schedule for the UE across RF bandwidthboundary or not. The scale of turn-on or turn-off can be per TTI,subframe, slot, or mini-slot basis in the time domain, e.g. gNB indicatefor each TTI, subframe, slot, or mini-slot, the functionality is turn-onor not (there may be default decision if there is no indication). Thescale of turn-on or turn-off can be per PRB, PRG, subband, or bandwidthportion basis in the frequency domain, e.g. gNB indicates for each PRB,PRG, subband, or bandwidth portion, the functionality is turn-on or not.In one embodiment, there may be default decision if there is noindication. The scale can jointly consider time domain and frequencydomain. The indication can be carried on a control channel used toschedule a data channel (in that TTI, subframe, slot, or mini-slot. Anexample is given in FIG. 25.

A seventh general concept is that UE reception bandwidth, e.g. bandwidthpart, does not map across RF bandwidth boundary of a base station. Inone embodiment, a UE is capable of receiving a bandwidth larger than abandwidth of a RF chain of a gNB. Alternatively, UE reception bandwidth,e.g. bandwidth part, can map across RF bandwidth boundary of a basestation while UE cannot receive a scheduling schedule a data channelwhose resource map across RF bandwidth boundary of a base station.Examples are given in FIGS. 26 and 27.

Throughout this application, base station, TRP, cell, gNB, and carriercould be used interchangeably. Furthermore, a base station could use aplurality of RF chains to transmit a carrier and each RF chain is usedto transmit channel or signal associated with a portion of bandwidth ofthe carrier.

Throughout the application, a UE could use a single RF chains to receivea carrier of a base station (or a portion of a carrier if a maximumbandwidth supported by the UE is less than bandwidth of the carrier).Alternatively, a UE could use a plurality of RF chains to receive acarrier or a portion of a carrier of a base station and each RF chain isused to receive channel or signal associated with a portion of bandwidthof the carrier or the portion of the carrier.

In one embodiment, a gNB could decide whether or how to scheduleresource blocks within a PRG to a UE according to whether PRB bundlingis applied by the UE. In one embodiment, the PRG could map cross a RFbandwidth boundary of the gNB.

In one embodiment, the gNB does not schedule resource block(s) withinthe PRG to UE(s) operating with PRB bundling. Furthermore, the gNB couldschedule resource block(s) within the PRG to UE(s) not operating withPRB bundling. Alternatively, the gNB could schedule resource block(s)within the PRG to UE(s) operating with PRB bundling wherein thescheduled resource block(s) within the PRG are transmitted by a same RFchain of the gNB. In one embodiment, a reception bandwidth of a UE couldmap across the RF bandwidth boundary. In one embodiment, UE could bescheduled with a data channel which maps across the RF bandwidthboundary.

In another embodiment, a gNB or UE could group resource blocks into PRGwherein all resource blocks within every PRG within a carrier bandwidthwould be transmitted by a single RF chain. Furthermore, different PRGmay be transmitted with different RF chain. In addition, a size of abandwidth of a RF chain can be equally divided by a size of PRGcorresponding to the bandwidth of the RF chain. Both sizes could beexpressed in a unit of PRB. In one embodiment, there is no PRGs mappingacross a RF bandwidth boundary of a gNB. Furthermore, sizes ofbandwidths of different RF chains could be different. In addition, sizesof bandwidths of PRG corresponding to bandwidths of different RF chainscould be different.

In another embodiment, a gNB or UE could group resource blocks into PRGwherein sizes of PRG do not follow non-increasing order in frequencydomain across a carrier bandwidth. Furthermore, sizes of PRG couldfollow non-increasing order in frequency domain within a first set ofPRGs in the carrier bandwidth, and sizes of PRG could follow increasingorder in frequency domain within a second set of PRGs within the carrierbandwidth.

In one embodiment, the gNB could configure a plurality of bandwidthportions which partition a whole carrier bandwidth. Furthermore, thebandwidth portions could be configured by a dedicated signaling to a UE.In addition, the bandwidth portions could be configured by a broadcastsignaling.

Size and location of bandwidth portions could be fixed (or pre-known) toUE or gNB. Also, sizes of PRG could follow non-increasing order infrequency domain within a bandwidth portion. In addition, sizes of PRGcould follow increasing order from PRG within a first bandwidth portionto a PRG within a second bandwidth portion. Sizes and/or locations ofPRG could also follow a predefined rule. More specifically, sizes and/orlocations of PRG could be determined according to a bandwidth of abandwidth portion. Alternatively, sizes and/or locations of PRG could beconfigured to UE with a dedicated signal or a broadcast signal. Inaddition, sizes and/or locations of PRG for different bandwidth portionscan be different. For example, a first bandwidth portion comprises PRGs(mostly) with size of 2 PRBs and a second bandwidth portion comprisesPRGs with (mostly) size of 3 PRBs. “Mostly” could mean PRG with evensmaller size may exist due to PRG size not equally dividing the firstbandwidth portion or the second bandwidth portion. A reception bandwidthof a UE could map across the RF bandwidth boundary. Furthermore, UEcould be scheduled with data a data channel which maps across the RFbandwidth boundary.

In another embodiment, a gNB could indicate boundary(s), e.g. RFbandwidth boundary, PRB bundling boundary, of a carrier to a UE.Alternatively, boundary(s) (e.g. RF bandwidth boundary, PRB bundlingboundary) of a carrier could be fixed or pre-known to a gNB or a UE. Theboundary is related to PRB bundling operation.

In one embodiment, a gNB does not transmit PRBs with a same manneracross the boundary(s). The PRBs could belong to a same PRG. In oneembodiment, a UE does not receive PRBs with a same manner across theboundary(s). The PRBs could belong to a same PRG across the boundary. Inone embodiment, receiving PRBs with a same manner means deriving channelestimation jointly for the PRB. The UE could receive PRBs with a samemanner wherein the PRBs belong to a same PRG which does not map acrossthe boundary(s). For example, when UE performs channel estimationaccording to PRB bundling, UE would derive joint channel estimation forPRG which does not map across the boundary. UE would not derive jointchannel estimation for PRG across the boundary(s). UE would deriveseparate/different channel estimations for PRB(s) on different side ofthe boundary(s).

In one embodiment, a gNB could indicate whether a functionality of PRBbundling is applied, activated, or turned-on or not to a UE.Furthermore, the indication may not be whether PMI/RI reporting isconfigured. In addition, the indication may not be a configuredtransmission mode of the UE. Furthermore, the functionality of PRBbundling could be configured for the UE. In addition, the UE could beconfigured with transmission mode supporting PRB bundling. In oneembodiment, the indication could tell the UE which TTI, subframe, slot,or mini-slot the functionality of PRB bundling is applied, activated, orturned-on. The indication could tell the UE which TTI, subframe, slot,or mini-slot the functionality of PRB bundling is not applied,activated, or turned-on. The indication could tell the UE whether for agiven TTI, subframe, slot, or mini-slot, the functionality of PRBbundling is applied, activated, or turned-on or not. The indicationcould tell that the UE in following TTIs, subframes, slots, ormini-slots, the functionality of PRB bundling is applied, activated, orturned-on. The indication could tell that the UE in following TTIs,subframes, slots, or mini-slots, the functionality of PRB bundling isnot applied, activated, or turn-on.

There may be some delay between a reception of the indication and UEaction of applied or not applied, activated or deactivated, turned-on orturned-off. The indication could tell the UE whether for a given PRB,PRG, subband, or bandwidth portion, the functionality of PRB bundling isapplied, activated, or turned-on or not. More specifically oralternatively, the indication could tell the UE that the PRB, PRG,subband, or bandwidth portion where the functionality of PRB bundling isnot applied, activated, or turned-on. More specifically oralternatively, the indication could be carried on a control channel.More specifically the control channel could be used to schedule a datachannel to the UE. More specifically or alternatively, the indicationcould be applicable to TTI(s), subframe(s), slot(s), or mini-slot(s)that the control channel is associated with. More specifically oralternatively, the indication could be applicable to the TTI(s),subframe(s), slot(s), or mini-slot(s) that the data channel isassociated with. More specifically or alternatively, the indicationcould be applicable to following TTI(s), subframe(s), slot(s), ormini-slot(s). More specifically or alternatively, the indication couldbe applicable to a certain number of TTI(s), subframe(s), slot(s), ormini-slot(s).

In another embodiment, reception bandwidth of a UE may not map across aboundary(s). The reception bandwidth could be a bandwidth part of theUE. The boundary(s) could be indicated by a gNB to the UE. Theboundary(s) could be a RF boundary of a gNB.

In another embodiment, reception bandwidth of a UE can map across aboundary(s). In one embodiment, in a given TTIsubfrmae, slot, ormini-slot, a data channel scheduled to the UE may not map across theboundary(s). In one embodiment, the reception bandwidth could be abandwidth part of the UE. In one embodiment, the boundary(s) could beindicated by a gNB to the UE. In one embodiment, the boundary(s) couldbe the RF boundary of a gNB.

FIG. 28 is a flow chart 2800 according to one exemplary embodiment. Instep 2805, a gNB decides whether to schedule resource blocks within aPRG to a UE or not according to whether a PRB bundling is applied by theUE. In one embodiment, the PRG could map cross a RF bandwidth boundaryof the gNB.

In step 2810, the gNB decides how to schedule resource blocks within thePRG to the UE or not according to whether the PRB bundling is applied bythe UE. In one embodiment, the gNB does not schedule resource block(s)within the PRG to the UE if the UE operates with PRB bundling.Alternatively, the gNB could schedule resource block(s) within the PRGto the UE if the UE does not operates with PRB bundling. Furthermore,the gNB could schedule resource block(s) within the PRG the UE if the UEoperates with PRB bundling wherein the scheduled resource block(s)within the PRG are transmitted by a same RF chain of the gNB.

In one embodiment, a reception bandwidth of the UE can map across the RFbandwidth boundary. Furthermore, the UE can be scheduled with a datachannel which maps across the RF bandwidth boundary.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a gNB,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the gNB (i) to decidewhether to schedule resource blocks within a PRG to a UE or notaccording to whether a PRB bundling is applied by the UE, and (ii) todecide how to schedule resource blocks within the PRG to the UE or notaccording to whether the PRB bundling is applied by the UE. Furthermore,the CPU 308 can execute the program code 312 to perform all of theabove-described actions and steps or others described herein.

FIG. 29 is a flow chart 2900 a flow chart according to one exemplaryembodiment. In step 2905, a gNB groups resource blocks into PRG(s),wherein all resource blocks within every PRGs within a carrier bandwidthof the gNB would be transmitted by a single RF chain of the gNB.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a gNB,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the gNB to groupresource blocks into PRG(s), wherein all resource blocks within everyPRGs within a carrier bandwidth of the gNB would be transmitted by asingle RF chain of the gNB.

FIG. 30 is a flow chart 3000 a flow chart according to one exemplaryembodiment. In step 3005, a UE groups resource blocks into PRG(s),wherein all resource blocks within every PRGs within a carrier bandwidthof a gNB would be transmitted by a single RF chain of the gNB.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE to groupresource blocks into PRG(s), wherein all resource blocks within everyPRGs within a carrier bandwidth of a gNB would be transmitted by asingle RF chain of the gNB. Furthermore, the CPU 308 can execute theprogram code 312 to perform all of the above-described actions and stepsor others described herein.

In the context of the embodiments illustrated in FIGS. 29 and 30 anddescribed above, in one embodiment, different PRGs could be transmittedwith different RF chains. Furthermore, a size of a bandwidth of a RFchain could be equally divided by a size of PRG corresponding to thebandwidth of the RF chain. In addition, the size could be counted in aunit of PRB.

In one embodiment, there may be no PRG mapping across a RF bandwidthboundary of the gNB. Furthermore, sizes of bandwidths of different RFchains could be different. In addition, sizes of bandwidths of PRGcorresponding to bandwidths of different RF chains could be different.

FIG. 31 is a flow chart 3100 a flow chart according to one exemplaryembodiment. In step 3105, a gNB groups resource blocks into PRG(s),wherein sizes of the PRG(s) do not follow non-increasing order infrequency domain across a carrier bandwidth.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a gNB,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the gNB to groupresource blocks into PRG(s), wherein sizes of the PRG(s) do not follownon-increasing order in frequency domain across a carrier bandwidth.

Furthermore, the CPU 308 can execute the program code 312 to perform allof the above-described actions and steps or others described herein.

FIG. 32 is a flow chart 3200 a flow chart according to one exemplaryembodiment. In step 3205, a UE groups resource blocks into PRG(s),wherein sizes of the PRG(s) do not follow non-increasing order infrequency domain across a carrier bandwidth.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE to groupresource blocks into PRG(s), wherein sizes of the PRG(s) do not follownon-increasing order in frequency domain across a carrier bandwidth.

In the context of the embodiments illustrated in FIGS. 31 and 32, in oneembodiment, PRG sizes could follow non-increasing order in frequencydomain within a first set of PRGs in the carrier bandwidth. PRG sizescould also follow increasing order in frequency domain within a secondset of PRGs within the carrier bandwidth.

In one embodiment, the gNB could configure a plurality of bandwidthportions which partition a whole carrier bandwidth. The bandwidthportions could be configured by a dedicated signaling to a UE, or abroadcast signaling. Furthermore, size and/or location of bandwidthportions could be fixed/pre-known to the UE and/or the gNB. In addition,PRG sizes could follow a non-increasing order in frequency domain withina first bandwidth portion. PRG sizes of PRG could also follow increasingorder from PRG within a first bandwidth portion to a PRG within a secondbandwidth portion. Alternatively, sizes and/or locations of PRG couldfollow a predefined rule.

In one embodiment, sizes and/or locations of PRG could be determinedaccording to a bandwidth of a bandwidth portion. Alternatively, sizesand/or locations of PRG could be configured to UE with a dedicatedsignal or a broadcast signal. Furthermore, sizes and/or locations of PRGfor different bandwidth portions could be different.

In one embodiment, a reception bandwidth of a UE could map across the RFbandwidth boundary. Furthermore, a UE could be scheduled with data froma data channel which maps across the RF bandwidth boundary.

FIG. 33 is a flow chart 3300 a flow chart according to one exemplaryembodiment. In step 3305, a gNB indicates boundary(s) within a carrierto a UE, wherein the boundary(s) is fixed or pre-known to the gNB and/orthe UE. In one embodiment, the boundary(s) could be a RF bandwidthboundary, or a PRB bundling boundary. Alternatively, the boundary(s)could be related to a PRB bundling operation.

In one embodiment, the gNB may not transmit PRBs with a same manneracross the boundary(s). Furthermore, the PRBs could belong to a samePRG.

In one embodiment, the UE may not receive PRB s with a same manneracross the boundary(s). Furthermore, the PRBs could belong to a same PRGacross the boundary.

In one embodiment, the UE could receive PRBs with a same manner whereinthe PRBs belong to a same PRG which does not map across the boundary(s).Furthermore, when the UE performs channel estimation according to PRBbundling, the UE could derive joint channel estimation for PRG whichdoes not map across the boundary. In addition, the UE may not derivejoint channel estimation for PRG across the boundary(s). Also, the UEcould derive separate or different channel estimations for PRB(s) ondifferent sides of the boundary(s).

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a gNB,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the gNB to indicateboundary(s) within a carrier to a UE, wherein the boundary(s) is fixedor pre-known to the gNB and/or the UE. Furthermore, the CPU 308 canexecute the program code 312 to perform all of the above-describedactions and steps or others described herein.

FIG. 34 is a flow chart 3400 a flow chart according to one exemplaryembodiment. In step 3405, a gNB indicates whether a functionality of PRBbundling is applied, activated, turned-on, or not to a UE.

In one embodiment, the indication could indicate whether or not PMI/RIreporting is configured. Furthermore, the indication is not a configuredtransmission mode of the UE.

In one embodiment, the functionality of PRB bundling could be configuredfor the UE. Furthermore, the UE could be configured with transmissionmode supporting PRB bundling.

In one embodiment, the indication could inform the UE which TTI,subframe, slot, or mini-slot, the functionality of PRB bundling isapplied, activated, or turned-on, or is not applied, activated, orturned-on. The indication could also inform the UE whether for a givenTTI, subframe, slot, or mini-slot, the functionality of PRB bundling isapplied, activated, turned-on, or not. Furthermore, the indication couldinform the UE that in following TTIs, subframes, slots, or mini-slots,the functionality of PRB bundling is applied, activated, or turned-on.In addition, the indication could inform the UE that in following TTIs,subframes, slots, or mini-slots, the functionality of PRB bundling isnot applied, activated, or turned-on.

In one embodiment, there may be some delay between a reception of theindication and the UE action of applied or not applied, activated ordeactivated, or turned-on or turned-off.

In one embodiment, the indication could inform the UE whether for agiven PRB, PRG, subband, or bandwidth portion, the functionality of PRBbundling is applied, activated, turned-on, or not. The indication couldalso inform the UE PRB, PRG, subband, or bandwidth portion where thefunctionality of PRB bundling is not applied, activated, or turned-on.

In one embodiment, the indication could be carried on a control channel.The control channel could be used to schedule a data channel to the UE.

In one embodiment, the indication could be applicable to TTI(s),subframe(s), slot(s), or mini-slot(s) the control channel associatedwith. The indication could also be applicable to TTI(s), subframe(s),slot(s), or mini-slot(s) the data channel associated with.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a gNB,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the gNB to indicatewhether a functionality of PRB bundling is applied, activated,turned-on, or not to a UE. Furthermore, the CPU 308 can execute theprogram code 312 to perform all of the above-described actions and stepsor others described herein.

FIG. 35 is a flow chart 3500 a flow chart according to one exemplaryembodiment. In step 3505, the UE receives a dedicated signaling whichconfigures a first bandwidth portion and a second bandwidth portionwithin a cell from a base station. In step 3510, the UE receives a firstconfiguration indicating a first precoding resource group (PRG) size forthe first bandwidth portion. In step 3515, the UE receives a secondconfiguration indicating a second PRG size for the second bandwidthportion.

In one embodiment, the UE determines PRGs within the first bandwidthportion according to the first configuration, the UE determines PRGswithin the second bandwidth portion according to the secondconfiguration, and the UE receives downlink data accordingly.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to receive adedicated signaling which configures a first bandwidth portion and asecond bandwidth portion within a cell from a base station, (ii) toreceive a first configuration indicating a first precoding resourcegroup (PRG) size for the first bandwidth portion, and (iii) to receivesa second configuration indicating a second PRG size for the secondbandwidth portion. Furthermore, the CPU 308 can execute the program code312 to perform all of the above-described actions and steps or othersdescribed herein.

FIG. 36 is a flow chart 3600 a flow chart according to one exemplaryembodiment. In step 3605, the base station transmits a dedicatedsignaling which configures a first bandwidth portion and a secondbandwidth portion within a cell to a UE. In step 3610, the base stationtransmits a first configuration indicating a first precoding resourcegroup size for the first bandwidth portion to the UE. In step 3615, thebase station transmits a second configuration indicating a second PRGsize for the second bandwidth portion to the UE.

In one embodiment, the base station determines PRGs within the firstbandwidth portion according to the first configuration, the base stationdetermines PRGs within the second bandwidth portion according to thesecond configuration, and the base station transmits downlink data tothe UE accordingly.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a basestation, the device 300 includes a program code 312 stored in the memory310. The CPU 308 could execute program code 312 to enable the basestation (i) to transmit a dedicated signaling which configures a firstbandwidth portion and a second bandwidth portion within a cell to a UE,(ii) to transmit a first configuration indicating a first precodingresource group size for the first bandwidth portion to the UE, and (iii)to transmit a second configuration indicating a second PRG size for thesecond bandwidth portion to the UE. Furthermore, the CPU 308 can executethe program code 312 to perform all of the above-described actions andsteps or others described herein.

In the context of the embodiments illustrated in FIGS. 35 and 36, anddescribed above, in one embodiment, the first bandwidth portion could bepartitioned by the first PRG size, and the second bandwidth portion ispartitioned by the second PRG size. Furthermore, sizes of PRGs couldfollow non-increasing order in frequency domain within the firstbandwidth portion, and sizes of PRGs could follow non-increasing orderin frequency domain within the second bandwidth portion.

In one embodiment, the first bandwidth portion could comprise a firstnumber of physical resource blocks (PRBs), and the second bandwidthportion could comprise a second number of PRBs.

In one embodiment, a plurality of PRGs within the first bandwidthportion could have the first PRG size, and a plurality of PRGs withinthe second bandwidth portion could have the second PRG size.

FIG. 37 is a flow chart 3700 a flow chart according to one exemplaryembodiment. In step 3705, the UE receives a configuration offunctionality of PRB bundling from a base station. In step 3710, the UEreceives an indication from the base station regarding whether thefunctionality of PRB bundling applies to a TTI or not.

In one embodiment, the UE receives downlink data in the TTI according tothe indication.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to receive aconfiguration of functionality of PRB bundling from a base station, and(ii) to receive an indication from the base station regarding whetherthe functionality of PRB bundling applies to a TTI or not. Furthermore,the CPU 308 can execute the program code 312 to perform all of theabove-described actions and steps or others described herein.

FIG. 38 is a flow chart 3800 a flow chart according to one exemplaryembodiment. In step 3805, the base station configures a UE functionalityof PRB bundling. In step 3810, the base station indicates to a UEwhether the functionality of PRB bundling applies to a TTI or not.

In one embodiment, the base station transmits downlink data in the TTIaccording to the indication.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a basestation, the device 300 includes a program code 312 stored in the memory310. The CPU 308 could execute program code 312 to enable the basestation (i) to configure a UE functionality of PRB bundling, and (ii) toindicate to a UE whether the functionality of PRB bundling applies to aTTI or not. Furthermore, the CPU 308 can execute the program code 312 toperform all of the above-described actions and steps or others describedherein.

In the context of the embodiments illustrated in FIGS. 37 and 38 anddescribed above, in one embodiment, the transmission time interval couldbe a subframe, a slot, or a mini-slot.

In one embodiment, indication of whether the functionality of PRBbundling applies to a transmission time interval (TTI) or not is carriedon a control channel.

In one embodiment, the control channel could be used to schedule a datachannel to the UE.

In one embodiment, the indication could be applicable to a transmissiontime interval the data channel associated with. The indication couldalso be applicable to a transmission time interval the control channelassociated with.

Various aspects of the disclosure have been described above. It shouldbe apparent that the teachings herein may be embodied in a wide varietyof forms and that any specific structure, function, or both beingdisclosed herein is merely representative. Based on the teachings hereinone skilled in the art should appreciate that an aspect disclosed hereinmay be implemented independently of any other aspects and that two ormore of these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. As an exampleof some of the above concepts, in some aspects concurrent channels maybe established based on pulse repetition frequencies. In some aspectsconcurrent channels may be established based on pulse position oroffsets. In some aspects concurrent channels may be established based ontime hopping sequences. In some aspects concurrent channels may beestablished based on pulse repetition frequencies, pulse positions oroffsets, and time hopping sequences.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, processors, means, circuits, and algorithmsteps described in connection with the aspects disclosed herein may beimplemented as electronic hardware (e.g., a digital implementation, ananalog implementation, or a combination of the two, which may bedesigned using source coding or some other technique), various forms ofprogram or design code incorporating instructions (which may be referredto herein, for convenience, as “software” or a “software module”), orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

In addition, the various illustrative logical blocks, modules, andcircuits described in connection with the aspects disclosed herein maybe implemented within or performed by an integrated circuit (“IC”), anaccess terminal, or an access point. The IC may comprise a generalpurpose processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, electrical components, opticalcomponents, mechanical components, or any combination thereof designedto perform the functions described herein, and may execute codes orinstructions that reside within the IC, outside of the IC, or both. Ageneral purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

It is understood that any specific order or hierarchy of steps in anydisclosed process is an example of a sample approach. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the processes may be rearranged while remaining within thescope of the present disclosure. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with theaspects disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module (e.g., including executable instructions and relateddata) and other data may reside in a data memory such as RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a harddisk, a removable disk, a CD-ROM, or any other form of computer-readablestorage medium known in the art. A sample storage medium may be coupledto a machine such as, for example, a computer/processor (which may bereferred to herein, for convenience, as a “processor”) such theprocessor can read information (e.g., code) from and write informationto the storage medium. A sample storage medium may be integral to theprocessor. The processor and the storage medium may reside in an ASIC.The ASIC may reside in user equipment. In the alternative, the processorand the storage medium may reside as discrete components in userequipment. Moreover, in some aspects any suitable computer-programproduct may comprise a computer-readable medium comprising codesrelating to one or more of the aspects of the disclosure. In someaspects a computer program product may comprise packaging materials.

While the invention has been described in connection with variousaspects, it will be understood that the invention is capable of furthermodifications. This application is intended to cover any variations,uses or adaptation of the invention following, in general, theprinciples of the invention, and including such departures from thepresent disclosure as come within the known and customary practicewithin the art to which the invention pertains.

What is claimed is:
 1. A method of operation of a User Equipment (UE),the method comprising: receiving a configuration for a first bandwidthportion and a second bandwidth portion of a system bandwidth of a cell,wherein the second bandwidth portion differs from the first bandwidthportion; receiving a configuration for a first precoding resource group(PRG) size for the first bandwidth portion; receiving a configurationfor a second PRG size for the second bandwidth portion, wherein thesecond PRG size is different from the first PRG size; determining eachof a plurality of PRGs within the first bandwidth portion according tothe first PRG size; and determining each of a plurality of PRGs withinthe second bandwidth portion according to the second PRG size.
 2. Themethod of claim 1, wherein the configuration for the first bandwidthportion and the second bandwidth portion is included in a dedicatedsignaling from a base station that indicates a division of the systembandwidth of the cell.
 3. The method of claim 1, wherein the firstbandwidth portion does not overlap with any part of the second bandwidthportion.
 4. The method of claim 1, wherein the configuration for thefirst bandwidth portion and the second bandwidth portion includes afirst bandwidth portion size, a first bandwidth portion location, asecond bandwidth portion size and a second bandwidth portion location.5. The method of claim 1, further comprising receiving downlink datafrom a base station.
 6. The method of claim 1, further comprisingpartitioning the first bandwidth portion by the first PRG size and thesecond bandwidth portion by the second PRG size.
 7. The method of claim1, wherein the first PRG size follows non-increasing order in frequencydomain within the first bandwidth portion, and the second PRG sizefollows non-increasing order in frequency domain within the secondbandwidth portion.
 8. The method of claim 1, wherein a plurality of thePRGs of the first bandwidth portion have the first PRG size, and aplurality of PRGs of the second bandwidth portion have the second PRGsize.
 9. A method of communications between a User Equipment (UE) and abase station (BS) in a cell, the method comprising: dividing a systembandwidth of the cell into a first bandwidth portion and a secondbandwidth portion, wherein the second bandwidth portion differs from thefirst bandwidth portion; defining a first precoding resource group (PRG)size for the first bandwidth portion; defining a second PRG size for thesecond bandwidth portion, wherein the second PRG size is different fromthe first PRG size; determining each of a plurality of PRGs within thefirst bandwidth portion according to the first PRG size; and determiningeach of a plurality of PRGs within the second bandwidth portionaccording to the second PRG size.
 10. The method of claim 9, furthercomprising the BS providing to the UE a dedicated signaling indicating aconfiguration for the division of the first bandwidth portion and thesecond bandwidth portion of the system bandwidth.
 11. The method ofclaim 10, wherein the configuration for the first bandwidth portion andthe second bandwidth portion includes a first bandwidth portion size, afirst bandwidth portion location, a second bandwidth portion size and asecond bandwidth portion location.
 12. The method of claim 9, whereinthe first bandwidth portion does not overlap with any part of the secondbandwidth portion.
 13. The method of claim 9, further comprisingreceiving downlink data from the base station.
 14. The method of claim9, further comprising partitioning the first bandwidth portion by thefirst PRG size and the second bandwidth portion by the second PRG size.15. The method of claim 9, wherein the first PRG size followsnon-increasing order in frequency domain within the first bandwidthportion, and the second PRG size follows non-increasing order infrequency domain within the second bandwidth portion.
 16. A method ofoperation of a Base Station (BS), the method comprising: dividing afirst bandwidth portion and a second bandwidth portion of a systembandwidth of a cell such that the second bandwidth portion differs fromthe first bandwidth portion; determining each of a plurality ofprecoding resource groups (PRGs) within the first bandwidth portionaccording to a first PRG size; determining each of a plurality of PRGswithin the second bandwidth portion according a the second PRG size,wherein the second PRG size is different from the first PRG size. 17.The method of claim 16, further comprising communicating to a UserEquipment (UE) a configuration for the first bandwidth portion and thesecond bandwidth portion of a system bandwidth of the cell, including afirst bandwidth portion size, a first bandwidth portion location, asecond bandwidth portion size and a second bandwidth portion location.18. The method of claim 17, further comprising communicating to a UE thefirst PRG size and the second PRG size.
 19. The method of claim 16,wherein the first PRG size follows non-increasing order in frequencydomain within the first bandwidth portion, and the second PRG sizefollows non-increasing order in frequency domain within the secondbandwidth portion.
 20. The method of claim 16, wherein a plurality ofthe PRGs of the first bandwidth portion have the first PRG size, and aplurality of PRGs of the second bandwidth portion have the second PRGsize.